News for hackers. Stuff that matters.
Re:Why the fuck are we templating YAML? (2019) by incrudible on Tuesday January 23, 2024 @09:56AM (#39104125)
An XML document without a schema is strictly worse than JSON without a schema. JSON with a schema is strictly better than XML with a schema. XML structure does not map neatly into the data types you actually want to use. You do not want to use a tree of things with string attributes, all over your code. If you do have a schema, the first thing you will want to do is turn your data into native language data types. After that point, the serialization method does not matter anymore, and XML would have just be slower. Designing a schema for XML is also more tedious than for JSON.
Re:Why the fuck are we templating YAML? (2019) by bayindirh on Tuesday January 23, 2024 @10:23AM (#39104570)
> XML structure does not map neatly into the data types you actually want to use.

> After that point, the serialization method does not matter anymore, and XML would have just be slower.

Considering I have mapped 3D objects to (a lot of) C++ objects containing thousands of facets under 12ms incl. parsing, sanity checking, object creation, initialization and cross linking of said objects on last decade's hardware, I disagree with that sentiment.

Regarding your first point, even without a schema, an XML shows its structure and what it expects. So JSON feels its hacked together when compared to XML in terms of structure and expressiveness.

It's fine for serializing dark data where people won't see, but if eyes need to inspect it XML is way way more expressive by nature.

Heck, you even need to hack JSON for comments. C'mon :)

Re:Why the fuck are we templating YAML? (2019) by mcculley on Tuesday January 23, 2024 @10:02AM (#39104199)
I enjoy JSON for internal stuff and where it does not matter that JSON is not very expressive. JSON Schema is a poor substitute for a proper schema. For anything where I am interfacing with another person or team, I send them a DTD or XSD, which documents the attributes and does not have nonsense like confusing integers and floating point values.

For quick and dirty, I agree about JSON. For serious data interchange, I use XML.

Re:Why the fuck are we templating YAML? (2019) by mcculley on Tuesday January 23, 2024 @10:48AM (#39104938)
> JSON with a schema is strictly better than XML with a schema.

I am baffled by this assertion. XML Schema (XSD) is much more expressive than JSON Schema.

Re:Why the fuck are we templating YAML? (2019) by incrudible on Friday January 26, 2024 @12:55PM (#39145530)
That is a bug, not a feature.
Re:Why the fuck are we templating YAML? (2019) by mcculley on Friday January 26, 2024 @01:36PM (#39146178)
Not to me. I have lots of data exchanging going on where the format is expressed well in XSD and in JSON Schema it is expressed through documentation, code, and a history of angry emails.
Re:Why the fuck are we templating YAML? (2019) by incrudible on Saturday January 27, 2024 @03:42PM (#39159631)
If it can't be expressed as a JSON schema, it's a bad idea. If it can be expressed by a JSON schema, it may be a good idea.
Re:Why the fuck are we templating YAML? (2019) by mcculley on Sunday January 28, 2024 @08:50AM (#39165709)
This does not match my experience.

Can you provide some clear explanation or examples of why having less power to express a schema is desirable?

Re:Why the fuck are we templating YAML? (2019) by incrudible on Tuesday January 30, 2024 @05:05PM (#39196520)
Paralysis of choice.
Re:Why the fuck are we templating YAML? (2019) by mcculley on Thursday February 01, 2024 @08:30AM (#39215702)
This remains an unconvincing argument.
Re:Why the fuck are we templating YAML? (2019) by incrudible on Friday February 02, 2024 @06:31AM (#39227499)
Not everybody needs convincing. JSON already won.
Re:Why the fuck are we templating YAML? (2019) by mcculley on Friday February 02, 2024 @07:19PM (#39236316)
It won in places where one does not need to express an integer larger than 2^53. Lots of us have harder requirements.