f n space main open parenthesis close parenthesis space open curly bracket line return indent print l n exclamation mark open parenthesis open quote hello world close quote close parenthesis semicolon line return close curly bracket
I know everyone is here for the same thing, and we’ve all been correcting this image since it showed up five years ago, but an Americano is not a black coffee.
It is however, coffee that is black, but if I ordered one and got the other, I’d know somethings up.
Also, I really don’t know why people drink americano. To me they just taste like cigarettes, but I’m currently drinking chicory so my opinion is moot.
Don’t drink the JSON coolaid. XML is fine. Better, in many cases, because XML files actually support comments.
In the modern programming world, XML is just JSON before JSON was cool. There was a whole hype about XML for a few years, which is why old programming tools are full of XML.
It’s funny but sad to see the JSON ecosystem scramble to invent all of the features that XML already had. Even ActivityPub runs on “external entities but stored as general purpose strings”, and don’t get me started on the incompatible, incomplete standards for describing a JSON schema.
It’s not just XML either, now there’s cap’n proto and protobuf and bson which are all just ASN.1 but “cool”.
<span style="color:#323232;">{ "key": "six",
</span><span style="color:#323232;"> "value": 6,
</span><span style="color:#323232;"> "comment": "6 is a bad number. Use five." }
</span>
IMHO: XML is a file format, JSON is a data transfer format. Reinventing things like RSS or SVG to use JSON wouldn’t be helpful, but using XML to communicate between your app’s frontend and backend wouldn’t be either.
"The spelling disk and disc are used interchangeably except where trademarks preclude one usage, e.g., the Compact Disc logo. The choice of a particular form is frequently historical, as in IBM’s usage of the disk form beginning in 1956 with the “IBM 350 disk storage unit”. "
lemmy.world
Oldest