But a lot of languages have native support for parsing JSON without the need for a library. When it’s handled by the language, it’s more likely to be done to spec, doesn’t increase bundle size (if that matters to you), and will be considered as updates to the language are made.
I can speak to go, ruby, and PHP: Their libraries for support is per-spec.
Json is pretty great, and sure, if someone wants to make RSS2, using JSON, that’d be fine. But, RSS came long before JSON was even an idea, and XML was the only way we figured out.
RSS’s format is, in fact, so old, there’s been a huge amount of time refining those language’s libs to support RSS just dandy. You never even need to look at the XML.
Idk maybe I’m wrong. I worked for a news outlet for a couple years and I just remember generating and parsing XML to be more work then generating a JSON feed.
It’s not even just parsing. I just remember crawling the parsed JSON tree to not be as nice as navigating a JSON object.
But a lot of languages have native support for parsing JSON without the need for a library. When it’s handled by the language, it’s more likely to be done to spec, doesn’t increase bundle size (if that matters to you), and will be considered as updates to the language are made.
I can speak to go, ruby, and PHP: Their libraries for support is per-spec.
Json is pretty great, and sure, if someone wants to make RSS2, using JSON, that’d be fine. But, RSS came long before JSON was even an idea, and XML was the only way we figured out.
RSS’s format is, in fact, so old, there’s been a huge amount of time refining those language’s libs to support RSS just dandy. You never even need to look at the XML.
Idk maybe I’m wrong. I worked for a news outlet for a couple years and I just remember generating and parsing XML to be more work then generating a JSON feed.
It’s not even just parsing. I just remember crawling the parsed JSON tree to not be as nice as navigating a JSON object.