I wish I could hear it again for the first time, top 10 knock knock joke

If we’re adding comments to json, can we add canonical support for trailing commas?

Just make JSON5 the new official version and I would be ok

_comment: "this is a comment"

carthinazation

xml

Carcinisation is the phenomenon of non crabs to evolve crab like characteristics. It is not the process of non crabs becoming true crabs.

In this case the language is trending toward JSON syntax, but it doesn't have to actually be JSON for carcinisation to be an applicable analogy.

Equals schmequals.
It could be a ⇨ and it would be the same as JSON because it is still a single symbol used as a separator.

a distinction without a difference

Now, if it took multiple separators, each giving some specific different meaning, then it would be a something else.

As someone who runs Home Assistant:
Fuck YAML.

Nah, yaml isn't great by virtue of itself but with what it competes with. I far, far prefer it to any other BS. Json is garbage for human creation and obviously toml due to above. XML... Obviously just for machines.

Again, only good because of its competition.

No way. You're telling me I can just write json instead?

Is there a reason? Norway!

I’ve never had this issue with Python, but makefile has given me plenty of whitespace issues.

There just needs to be one universal standard that handles everyone’s use cases

I can kind of understand it after having to work with an XML file where users encoded data into comments for no good reason. But yeah, it does make JSON awkward for lots of potential use-cases.

Coming from powershell scripting, every string is put in quotes and to be printed strings with variables are put in $($var) (e.g. Write-Host "Example-Issue: $($IssueVariable)")
Saves me the trouble of hoping that $IssueVariable isnt interpreted as a string butbas a variable by PowerShell.

Or by configuring your parser.

I do agree there are plenty of annoyances that shouldn't exist in YAML but do because someone had an opinionated belief at one point, though. For example, it shouldn't try to guess that "yes", "no", "y", and "n" are truthy values. Let the programmer handle that. If they write true/false, then go ahead and consider those truthy. Times can also be a bit of a pain - iirc writing 12:00 is supposed to be interpreted as 0.5 - but at least that's something you can work around.

But there's plenty in that article that are only problems because the writer made them problems. Every language lets you make mistakes, markup languages aren't any different. It's not a bad thing that you can write strings without quotes. It's not forcing you to do so. Anchors also make it simple to reuse YAML and they're completely optional. The issue with numbers (1.2 stays as 1.2 while 1.2.3 becomes "1.2.3" is very nitpicky. It's completely reasonable for it to try to treat numbers as numbers where it can. If type conversion is that big of an issue for you, then I really doubt you know what you're doing.

On top of all this, YAML is just a superset of JSON. You can literally just paste JSON into your YAML file and it'll process it just fine.

I'm not saying it's perfect, but if you want something that's easy to read and write, even for people who aren't techy, YAML is probably the best option.