…from people who seem to refuse to install paredit or coloring plugins for either? ps lisp syntax ftw, it’s a feature!
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.
sometimes, a script needs to be edited in a plain text editor, without having access to an lsp or any other dev tools.
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.
No, YAML can fuck right off. I hate that this shit format is used for cloud stuff.
YAML is the Excel of data formats due to the Norway Problem
OK, that’s excessively “convenient” for booleans. But I don’t get the passionate YAML hate, seems like a simple enough language for config. Didn’t have the pleasure (“pleasure”?) to work with it though, so what’s why else is it shitty?
A property can have the wrong indentation and it would still be a syntactically correct yaml. It’s hard to distinguish whether a line is wrongly indented or not. Copy and paste a line and mistakenly use the wrong indentation, and the entire production breaks.
In json it’s much harder to do similar mistakes.
since yaml is just a superset of json, you can easily avoid all problems like this
yaml is like a less strict json for me
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.
I hate YAML so much