I feel that Yaml sucks. I understand the need for such markup language but I think it sucks. Somehow it’s clunky to use. Can you explain why?
I feel that Yaml sucks. I understand the need for such markup language but I think it sucks. Somehow it’s clunky to use. Can you explain why?
Any language in which whitespace has syntactic value is intrinsically flawed.
Can’t speak to your specific issues, but that’s why yaml will always suck.
As a serialization format, agree 100%, but would Python really be better if it switched to braces?
Yes, I think so. The downside with Python comes when refactoring the code. There’s always this double checking if the code is correctly indented after the refactor. Sometimes small mistakes creep in.
It’s really hard to tell when Python code is incorrectly indented. It’s often still valid Python code, but you can’t tell if it’s wrong unless you know the intention of the code.
In order languages it’s always obvious when code is incorrectly indented. There’s no ambiguity.
I think this is just familiarity. I never have issues with indentation, but when refactoring js I’m always like hey who’s fucking brace is this
It’s only hard to tell indentation in Python when the code block gets longer than about a screen, which is usually a sign the code should be refactored into smaller methods.
People hate hearing that they are bad coders 😂
You and the other guy are saying to focus on writing code with less indentation and using smaller methods, and you both got downvoted.
I fully agree, small methods all the way, and when that’s not possible it’s time to refactor into possibility!
They hated him because he spoke the truth
As someone who has been working in Python a ton for the last couple years, it’s amusing to me how many downvotes you’re getting for simply noting that good code style and tight, terse, modularized implementation of business logic more or less addresses the issue. Because it absolutely does in the vast majority of cases.
Or a sign you should get a bigger screen 😂 (j/k)
Can address it by writing code that doesn’t depend much on indentation, which also makes code more linear and easier to follow.
Yes, totally agree, and it applies to formats and language syntaxes even if braces are used.
To be pendantic, it’s level of indentation in Python that has semantic meaning, not whitespace.
The end of line also has semantic meaning. Both indentation and eol are whitespace.
Indentation can be (and should be) tabs, EOL is it’s its own thing either \n or CRLF which Python source code did actually care about as recently as 2.3.
Assumptions like this is why most people should stick to verbose languages with lots of guardrail braces.
Yes. A thousand times, yes.
Yes it would - look at optional braces for short if expressions in C family languages and why it’s so discouraged in large projects. Terminating characters are absolutely worth the cost of an extra LoC
False dichotomy. Optional braces are bad practice because they mislead the programmer that is adding an additional clause to the block.
This misleading behavior wouldn’t happen in Python, as it would either be invalid syntax, or it would be part of the block.
Indentation problems are pretty obvious to the reader. Even more than missing or unbalanced braces.
That misleading behavior does happen in Python. The next programmer that comes along can’t tell if the original programmer fucked it up and didn’t unindent to put a statement outside of the block or if they meant to put it inside the block. I’ve debugged this one too many times and it takes hours each time because it’s impossible to see the bug at all!!
The misleading behavior is about what you expect to execute in the source code you’re looking at vs what’s actually executed.
What you describe is a logic ambiguity that can happen in any program / language.
I don’t agree. It’s a direct result of whitespace, which does not happen if you don’t use whitespace. For example it can happen in Java and kotlin, but only if you use if statements without braces, which you pretty much never see. If you do see it you know to look out for the exact issue I described. That’s not possible in Python, since there is no alternative.
They may be obvious to the reader but they may be impossible to see if tabs and spaces are mixed together.
Closing tokens are always clearer.
yes, from my other comment
but that’s easily fixed with an editor setting - on the other hand, unbalancing braces (and not realizing it) is too easy all the time.
I started in C before moving on to C++, Java, Ruby and Python.
I’ve had more bugs from missing braces than from misaligned whitespace because the latter is far more obvious when looking at a block of code.
Compilation error or run time errors? One is a gift and the other is a curse.
PHP likes to have a word with you. (:
Like what?
Gonna whisper what the first word in “PHP” stands for
PHP?
I’m fine with python, because it’s consistent. In C I get nervous every time I see it.
goto fail;
If nothing else it enforces readable code which I think is a good thing.
It’s the only time that tabs Vs spaces really riles me up. So annoying when everyone has different tab lengths
Not any language. I code professionally in F# which has semantic whitespace and it has literally never been an issue for me or my team. In contrast to Python, it’s a compiled language and the compiler is quite strict, so that probably helps.
I now use Scala 3, and very happy with syntactic whitespace (combined with an intelligent compiler)
YAML sucks because, among other things, indenting it is not obvious.
In contrast, the only mistake of Python when it comes to whitespaces was allowing hard tabs, which makes it too easy to mix them if your editor is not configured.
Improper indentation stands out more than missing or unbalanced braces and it’s really not an issue to delimit code blocks.
deleted by creator
In any modern editor it is configurable with spaces too
What “it” is configurable? If the code is indented with 4 spaces, it is indented with 4 spaces. You can configure your editor to indent with 1 space if you want, but then your code is not going to respect the 4 spaces of indentation used by the rest of the code.
I repeat, the only accessible indentation option is using tabs. This is not an opinion because every other option forces extra painful steps for those with vision issues (including, but not limited to, having to reformat the source files to tabs so they can work on them and then reformat them back to using spaces in order to commit them)
Haskell supports both semantic whitespace and explicit delimiters, and somehow almost everybody that uses the language disagrees with you.
But anyway, for all the problems of YAML, this one isn’t even relevant enough to point out. Even if you agree it’s a problem. (And I agree that the YAML semantic whitespace is horrible.) If YAML was a much better language, it would be worth arguing whether semantic whitespace breaks it or not.
Yeah but Haskell is mostly used by mathematicians…