…from people who seem to refuse to install paredit or coloring plugins for either? ps lisp syntax ftw, it’s a feature!
I hate YAML so much
Who hates s-expressions? They’re elegant as fuck…
Python, on the other hand, deserves all the hate it gets for making whitespace syntactically significant - I even prefer Go’s hamfisted
go fmt
approach to a forced syntax to python’s bullshit.I dgaf about indices starting at 0 or 1, I can deal with case-insensitivity, but syntactically significant whitespace drives me up the wall.
What’s so hard to understand about it? It’s how you should format your code anyway. Only it’s enforced.
It’s quite often I have to second guess whether the code is correctly intended or not. Is this line supposed to be part of this if block or should I remove that extra indentation? It’s not always entirely obvious. Extra troublesome during refactors.
In other languages it’s always obvious when a line is incorrectly indented.
sometimes, a script needs to be edited in a plain text editor, without having access to an lsp or any other dev tools.
You take that back, python is my homie!
In all seriousness, I freely admit that I’m biased towards python because it was my first language and remains my favorite. I use an IDE for anything but the simplest scripts, so I’ve very rarely had any issues with spacing.
I hate em cos regardless of language auto formatter takes care of everything. So now im typing extra characters and fucking shit up and confusing myself when moving code between scopes.
I agree but still you can oftentimes expect that the average person’s initial reaction to be somehow reluctant… until they understand it. it’s like those foods and drinks that you might need to try a couple times before you start enjoying them.
Oh, definitely, they can look bizarre and confusing before you understand them.
In 20 years of using Python, I never had one issue with the indentation. Use spaces all the time, use PyCharm, and that’s it.
Whitespace is statistically insignificant in Python.
I love python: Fight me IRL.
fine i will take the bait: thats 5 spaces
As long as the next line also has 5 spaces, that’s fine. Python only complains about inconsistency, not the exact number of spaces/tabs.
Make, on the other hand… Ugh.
What, you don’t like tabs and spaces being syntactically different?
(Sarcasm/deadpan detected but I’ll respond anyways).
Not when they are visibly the same and the spaces have no other meaning in that context.
Not to mention tabs being annoying in general because of how badly it works to adjust the distance of tab stops. That doesn’t really affect this particular case, but it’s why I generally use spaces instead of tabs.
Most of the annoyance is from vim recognizing that spaces are an error in makefile recipes but still using them unless I copy paste a tab in, including when I hit enter on a line that is using a tab already. It matches the indentation but uses spaces instead of tabs. I’m sure there’s a way to adjust vim config to fix this, but I have yet to acquire the esoteric knowledge required to do so.
If by vim you mean neovim
vim.api.nvim_create_autocmd(“fileType”, { group = file_type_group, pattern = “make”, command = “setlocal ts=4 sts=4 sw=4 noexpandtab”, })
Slap this in your config, done
Nah, it’s just vim in my work env. But thanks anyways, I appreciate that you tried!
Go home OP, you’re drunk.
And give us your keys, you’ve had too much minimalism to drive.
Load-bearing whitespace is a mistake.
I don’t get why people hate semantic whitespace. The whitespace would be there anyway, and if anything it’s easier to read as long as you avoid 15 nested if statements, and you’re not using a dynamically typed abomination like python.
S-expressions are a hack because the Lisp devs didn’t know how to make an actual compiler, and instead had the users write the syntax tree for them. (For legal reasons I am being facetious).
In all honesty, I can understand the reason people love s-expressions, but to me they’re just unreadable at a glance.
Semantic whitespace is awful because whitespace (something that you can’t actually see) has meaning in how the program runs. Braces
{
}
for scopes gives you the ability to easily tell at a glance where a scope ends. Whitespace doesn’t allow for that. Especially, especially when you can accidentally exit a scope (two new lines in a row with Python) and it’s not actually an error (Pythons global scope). Yeah formatters and linters make this less of an issue but it sucks… Languages with legible symbols for scoping are significantly easier to reason about, seeend
symbols in Lua.S-expressions are a hack because the Lisp devs didn’t know how to make an actual compiler, and instead had the users write the syntax tree for them. (For legal reasons I am being facetious).
Just for anyone thinking you are serious; https://en.wikipedia.org/wiki/M-expression I love how S-expression existed.
McCarthy had planned to develop an automatic Lisp compiler (LISP 2) using M-expressions as the language syntax and S-expressions to describe the compiler’s internal processes. Stephen B. Russell read the paper and suggested to him that S-expressions were a more convenient syntax. Although McCarthy disapproved of the idea, Russell and colleague Daniel J. Edwards hand-coded an interpreter program that could execute S-expressions.[2] This program was adopted by McCarthy’s research group, establishing S-expressions as the dominant form of Lisp.
And for anybody thinking of implementing M-expressions, look at Wolfram Mathematica, which is the only popular M-expression-oriented language. It turns out that high-level graph-rewriting semantics are difficult to make efficient! (If you want to try, you might also want to look at GHC or other efficient graph-rewriters to see what the state of the art is like outside Planet Wolfram.)
I literally can’t see whitespace, it gives me headaches looking for it. With brackets, I can get bracket matching in my IDE.
ITT: Developers who think their code is readable complaining about Python and YAML.
Might just be me but YAML is some of the least readable shit I’ve ever used.
Honestly, I agree. But I don’t think Python is anywhere near that bad.
I write my short hand notes in yaml.
People with bracketed languages just want to write the most unreadable code ever to feel superior.
Clearly, the superiour mode is to just use keyword based scoping (à la Ruby
do ... end
). When I was a kid I read an OBSCENE MAGAZINE where I saw a Forth program godup dup dup
and I was like “ok so what’s the problem here? Things happen and everything is just keywords?” and my young mind was corrupted forever I guessyou’ll pry my END command from my cold, dead hands…
Haskell does both! Most people prefer to use whitespace when writing Haskell but it’s not required. Braces and semicolons are preferred if you’re going to be generating Haskell code.
Everyone that prefers whitespaces over parentheses is an animal.
Meow.
moo
Yep! Most of us are even homo sapiens!
People who prefer significant white space over bracket & brace blocks and semicolons are animals
People are animals.
It’s fascinating how s-expressions are both data type and language syntax. Such power. Only other time I saw something remotely like this was XSLT & XML, which I admittedly do not miss one bit.
Python has one of the worst syntaxes out there
This post made me go try something in clojure again and man I forgot just how fucking good the language is. Everything fits together so nicely.
I like them both. But I only use lisp for fun.