Well, that’s a blast from the past.
Introduction to Atom
11–20 of 71 posts
Re: Introduction to Atom
#12Earlier quoted context omitted.
No, this is just old. Pity though. RSS / Atom was a fantastic concept and it’s a real pity big tech killed them off.
Meh. Big tech didnt kill it off, it was already dead at that point. Sometimes things just arent popular no matter how much we might want it to be.
Google Reader was uber popular at a time, then Google decided that syndication of articles, with comments, had to be an exclusive feature of their Facebook-esque Google+.
Re: Introduction to Atom
#13First 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.
I don't reach for it often but I've been around the block a bit, CC processors in the iPad point of sale I built circa 2010 used it and it seemed a bit off/unnecessary.
In retrospect, its useful for creating islands of sanity/enforcement in a codebase. Lightweight way to give type annotations across organizational boundaries.
> we use an XML parser to parse it to JSON and even then it's not perfect
I can't quite picture this: how does one parse XML to JSON? I assume there's code that's parsing XML and returning a JSON object? What would make this not perfect, other than a poor implementation of the translator? Would them using JSON help? If JSON is a less expressive format than JSON, is it possible to 100% translate their XML to JSON?
Re: Introduction to Atom
#14Earlier quoted context omitted.
No, this is just old. Pity though. RSS / Atom was a fantastic concept and it’s a real pity big tech killed them off.
Nothing is killed. It still exists, it's an open protocol after all. And I choose to use it, it's pretty fun to calmly follow around 2000 feeds from - mostly - blogs from HN. And cars... I need my car blogs.
[dead]
Re: Introduction to Atom
#15Earlier quoted context omitted.
No, this is just old. Pity though. RSS / Atom was a fantastic concept and it’s a real pity big tech killed them off.
Nothing is killed. It still exists, it's an open protocol after all. And I choose to use it, it's pretty fun to calmly follow around 2000 feeds from - mostly - blogs from HN. And cars... I need my car blogs.
Is there any platform for sharing what feeds we follow? Would love to discover some new blogs.
Re: Introduction to Atom
#16At 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.
Re: Introduction to Atom
#17IIRC, Aaron Swartz was one of the contributors to the format. RIP.
Re: Introduction to Atom
#18At 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.
Re: Introduction to Atom
#19Earlier 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.
I don't reach for it often but I've been around the block a bit, CC processors in the iPad point of sale I built circa 2010 used it and it seemed a bit off/unnecessary. In retrospect, its useful for creating islands of sanity/enforcement in a codebase. Lightweight way to give type annotations across organizational boundaries. > we use an XML parser to parse it to JSON and even then it's not perfect I can't quite pict…
> useful for creating islands of sanity/enforcement in a codebase
Thanks for the insight! Is this what JSDoc/Swagger is now used for?
> I can't quite picture this: how does one parse XML to JSON?
I'm not sure actually. I haven't personally seen the code, I just hear my coworkers always lambasting that API provider for their usage of XML. Maybe it's just their lack of documentation that sucks, but it's become a running joke whenever we get a new partner that the team integrating it jokes that their API is XML.
Re: Introduction to Atom
#20Earlier quoted context omitted.
Nothing is killed. It still exists, it's an open protocol after all. And I choose to use it, it's pretty fun to calmly follow around 2000 feeds from - mostly - blogs from HN. And cars... I need my car blogs.
Is there any platform for sharing what feeds we follow? Would love to discover some new blogs.
Closest thing I can think of is this one: https://feedland.org
Or you create a blog for yourself and you make a blogroll.
As for discovering new blogs, couple of options but there are more out there: https://ooh.directory, https://blogroll.org/