So, in YAML you can only use leading spaces. Leading tabs are an error. This confusion of yours is not at all present in the actual thing you're talking about. And if you mix them in json god help you if your editor settings don't match someone else's because you might be looking at something nearly incomprehensible that won't error or warn at all.
I mean, have you ever actually looked at a code file of any sort with mixed tabs and spaces when the person who wrote the file had a different tab stop than you? This is a readability problem no matter what. Forcing you to have sane indentation is a feature of whitespace-sensitivity, not a bug.
What exactly do you think trailing whitespace does?
If I'm smoking something, at least I've used the things I'm talking about instead of spreading weird FUD.
> at least I've used the things I'm talking about instead of spreading weird FUD.
> A lot of JSON becomes pure noise: "{{[[{[{{[".
Pro-tip: if you are going to call someone out for not knowing a format and spreading FUD, don't post things where you do the same exact thing. It pretty much invalidates the criticisms you've been making as it says "I don't know what I'm talking about, here is proof."
That'd be cute if what I said there didn't come from experience, even if I did exaggerate the specifics.
Yes, the specific sequence of tokens is not valid because a list obviously can't be a key. The idea is still the same. I'll fix it so it is a valid sequence of tokens that's just as confusing: "}}}]}]}}"
honestly that's a code smell in any data serialisation notation. if you really did have a data structure like that it would manifest in yaml as an indentation 32 space characters. If you adhere to the 78 column rule, you've squeezed most of your data to the right of almost half your screen.
Anyways, invisible syntax errors still suck. At least with json you can (eventually) figure out your braces are unbalanced. Or use a syntax highlighter to spot the problem. No syntax to highlight if you have a problem with yaml.
So, in YAML you can only use leading spaces. Leading tabs are an error. This confusion of yours is not at all present in the actual thing you're talking about. And if you mix them in json god help you if your editor settings don't match someone else's because you might be looking at something nearly incomprehensible that won't error or warn at all.
I mean, have you ever actually looked at a code file of any sort with mixed tabs and spaces when the person who wrote the file had a different tab stop than you? This is a readability problem no matter what. Forcing you to have sane indentation is a feature of whitespace-sensitivity, not a bug.
What exactly do you think trailing whitespace does?
If I'm smoking something, at least I've used the things I'm talking about instead of spreading weird FUD.