Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Introduction to Atom

validator.w3.org

Post reply on HN
Print view View original

21–30 of 71 posts

Re: Introduction to Atom

#21

Post by deaddodo »

abustamam wrote: post #9
intrasight wrote: post #4

First iteration of Google's APIs were atom. I do miss XML.

One of the API providers I use at work returns responses in XML and we use an XML parser to parse it to JSON and even then it's not perfect. What do you like about XML? I feel like I'm missing something.

The main benefit of XML over JSON is that it is structured, and can be associated with Schema's for built in validation.

Obviously, that's only a benefit if you care about and utilize those features; most teams doing JSON integrations will just build those into the consumer in lieu of them being provided by the transport. But it is something that some people (especially larger enterprise organizations) value.

Re: Introduction to Atom

#23

Post by pletnes »

hnlmorg wrote: post #6
perrohunter wrote: post #2

what is old is new again?

No, this is just old. Pity though. RSS / Atom was a fantastic concept and it’s a real pity big tech killed them off.

Lots of sites publish outages, incidents, downtime over RSS/atom. Works great for monitoring, post them into slack with a bot and you can start a discussion thread about that incident where you first hear about it.

Re: Introduction to Atom

#24

Post by dolmen »

deaddodo wrote: post #21
abustamam wrote: post #9

Earlier quoted context omitted.

One of the API providers I use at work returns responses in XML and we use an XML parser to parse it to JSON and even then it's not perfect. What do you like about XML? I feel like I'm missing something.

The main benefit of XML over JSON is that it is structured, and can be associated with Schema's for built in validation. Obviously, that's only a benefit if you care about and utilize those features; most teams doing JSON integrations will just build those into the consumer in lieu of them being provided by the transport. But it is something that some people (especially larger enterprise organizations) value.

JSON is structured (not plain text to be analyzed by an IA). JSON has JSON Schema.

In addition, JSON is easier to parse and to map to common data structures of programming languages.

Re: Introduction to Atom

#25

Post by theshrike79 »

abustamam wrote: post #9
intrasight wrote: post #4

First iteration of Google's APIs were atom. I do miss XML.

One of the API providers I use at work returns responses in XML and we use an XML parser to parse it to JSON and even then it's not perfect. What do you like about XML? I feel like I'm missing something.

XLM had DTDs and Schemas 20 years ago.

JSON is still figuring it out.

Re: Introduction to Atom

#27

Post by riffraff »

echelon wrote: post #18
rippeltippel wrote: post #16

At this point, developers have named so many projects "Atom" that there are officially more Atoms in the world than there are atoms in the universe.

This one is (was) pretty important. The hyperscalers stopped that timeline from winning, though.

How is this the hyperscalers fault?

YouTube had atom feeds and I don't think Amazon and Microsoft have relevant syndication.

Meta is surely responsible but that's it, imo.

Re: Introduction to Atom

#28

Post by echelon »

riffraff wrote: post #27
echelon wrote: post #18

Earlier quoted context omitted.

This one is (was) pretty important. The hyperscalers stopped that timeline from winning, though.

How is this the hyperscalers fault? YouTube had atom feeds and I don't think Amazon and Microsoft have relevant syndication. Meta is surely responsible but that's it, imo.

Google on several occasions took moves to make the web less semantic.

They dumped microformats and standards in favor of soupy error tolerant formats that benefitted their search engine and made it harder for other efforts to make information shareable and accessible.

They wanted it to be easy to get information in, but for you to have to go through them to get information out.

Re: Introduction to Atom

#29

Post by riffraff »

eterevsky wrote: post #22

It was an alternative to RSS from 20 years ago that didn't catch on.

I think it caught on well enough, platforms such as Wordpress still support it out of the box (I just checked my blog, it works).

I liked Atom's clean design but it felt it was mostly pushed by Google (I may be misremembering) and in the end the syndicated web faded into obscurity anyway.

Re: Introduction to Atom

#30

Post by erk__ »

riffraff wrote: post #27
echelon wrote: post #18

Earlier quoted context omitted.

This one is (was) pretty important. The hyperscalers stopped that timeline from winning, though.

How is this the hyperscalers fault? YouTube had atom feeds and I don't think Amazon and Microsoft have relevant syndication. Meta is surely responsible but that's it, imo.

YouTube still does
I don't think they are linked to anywhere but the url is http://www.youtube.com/feeds/videos.xml?channel_id=
Post reply on HN