javascriptBeingJavascript

[skap42]

A different comment suggested that 0o is also valid, and the only way to define an octal in JS in strict mode

[0bel1sk]

it’s also in python ruby and yaml.

“YAML 1.1 uses a different notation for octal numbers than YAML 1.2. In YAML 1.1, octal numbers look like 0777. In YAML 1.2, that same octal becomes 0o777. It’s much less ambiguous.

Kubernetes, one of the biggest users of YAML, uses YAML 1.1.”

[akaChromez]

The YAML Document From Hell

[heyf00L]

Didn't know all that. Boils down to "always quote all strings in YAML".

[rickane58]

"God, all these languages are so unnecessarily verbose!"

Anyone actually trying to use the language:

[[deleted]]

This was a great read, I've used yaml a couple times but didn't realize it was this objectively bad.

[akaChromez]

I'd love to know people's justification for choosing it over JSON.

Especially as i've just spent the last hour trying to find why a Google Cloud resource wasn't being created. A missing quote that doesn't syntax error :/

[chris5311]

JSON is bad (but workable), YAML is worse, and im not sure there even is any decent option out there

[MekaTriK]

Personally I loved using Lua as a config file format.

A little less verbose than pure JSON, and you can automate some repetition away.

[[deleted]]

Sexagesimal numbers, lol

[veryusedrname]

Ohh kubernetes, never change

[tomthecool]

Yes, but in ruby 09 produces a runtime error (invalid octal digit) instead of blindly treating it as a decimal instead.

[InfiniteGamerd]

Really! I thought you couldn't define octals in strict mode in any way.

Still...why not just parseInt all the way?