Live data from Hacker News

Atom is better than RSS, in ways that matter

chrismorgan.info

91–100 of 111 posts

Re: Atom is better than RSS, in ways that matter

#91
post #71

Earlier quoted context omitted.

And those three ways to encode a title. Do I really imagine that every parser is going to undo the double-encoding correctly? Or XHTML conversion if I use a namespace prefix?

… yes? It’s simple XML parsing, and then taking it as text, serialised HTML, or an already-parsed DOM tree. You are using an actual XML parser, right? In most environments it’s no harder, and in browsers themselves (which is where half of it is consumed) it’s arguably easier .

the DOM tree is going to say either html:code or {http://something}code neither of which is just code.

Re: Atom is better than RSS, in ways that matter

#93

If you publish content, Atom is the superior format. All the parsers support it so there's no argument there against using it. You use it, everything should work just fine. There are no real downsides. The issue with RSS of course is that there is a lot of really crappy and ancient code out there that should have died a long time ago written in languages like PHP, Ruby, etc. by people who did not really care about de…

[flagged]

Re: Atom is better than RSS, in ways that matter

#94
post #91

Earlier quoted context omitted.

… yes? It’s simple XML parsing, and then taking it as text, serialised HTML, or an already-parsed DOM tree. You are using an actual XML parser, right? In most environments it’s no harder, and in browsers themselves (which is where half of it is consumed) it’s arguably easier .

the DOM tree is going to say either html:code or {http://something}code neither of which is just code.

When an XML document contains HTML, the DOM representation is of elements in the http://www.w3.org/1999/xhtml namespace.

When you parse a document or fragment that is in HTML syntax, the DOM representation is of elements in the http://www.w3.org/1999/xhtml namespace.

There is no difference.

Re: Atom is better than RSS, in ways that matter

#95
post #31

I agree that Atom is easier to use and better defined in some ways. But why on earth would you want to put unrestricted HTML in the title in the first place? How is a reader supposed to handle that? It's just a weird thing to allow. In practice, the differences between the syndication formats don't really matter. Today even less than when they were created, as a solution for most of the differences is just a prompt a…

Consider the title of my article: “Atom is better than RSS, in ways that matter ”. That emphasis belongs there, and it’s mildly bad to lose it. (For presentation on my own site, I also control the line break position on larger screens; but that wouldn’t be appropriate for feeds, where you can’t control the presentation.) We accept that sentences can have formatting, and headings can have formatting, so why shouldn’t…

Because the title appears next to a bunch of other titles.

It should be consistent, or else compromise browsing.

The content has no such situation.

Re: Atom is better than RSS, in ways that matter

#96
post #7

Earlier quoted context omitted.

What? Not at all. RSS is a product category. Many RSS feeds are, if you look into them, Atom. Your RSS reader just doesn't bother to tell you, because why would you care? Try putting a Betamax tape into a VHS VCR and see if you can watch it.

Atom is a response to not wanting to support backwards compatibility like RSS does in order to improve things. https://web.archive.org/web/20080216234454/http://www.sixapa... It's explicitly a different thing. This is like pointing at the monitor of a desktop computer and saying, "that's the computer". It is effective to communicate with people who aren't interested in computers, but it's also not true and the distin…

Which of the nine incompatible versions of RSS supports backwards compatibility? https://web.archive.org/web/20110726002019/http://diveintoma...

Re: Atom is better than RSS, in ways that matter

#97
post #91

Earlier quoted context omitted.

the DOM tree is going to say either html:code or {http://something}code neither of which is just code.

When an XML document contains HTML, the DOM representation is of elements in the http://www.w3.org/1999/xhtml namespace. When you parse a document or fragment that is in HTML syntax, the DOM representation is of elements in the http://www.w3.org/1999/xhtml namespace. There is no difference.

Hope your parser implements all this correctly!

Re: Atom is better than RSS, in ways that matter

#99
post #78

Earlier quoted context omitted.

I was responding to the generic comment that: > pretty much no-one uses either of them

And I stand with that phrase. I'm pretty sure that are more VHS users than RSS these days. It's not strictly zero, but it's a negligible fraction of internet users.

I don't disagree. But I would also assert the absolute number of RSS users is probably higher than it has ever been. And that's what matters, not what "most people do" now that there are far more non-technical users on the internet than ever before.

Re: Atom is better than RSS, in ways that matter

#100
post #97

Earlier quoted context omitted.

When an XML document contains HTML, the DOM representation is of elements in the http://www.w3.org/1999/xhtml namespace. When you parse a document or fragment that is in HTML syntax, the DOM representation is of elements in the http://www.w3.org/1999/xhtml namespace. There is no difference.

Hope your parser implements all this correctly!

It’s genuinely easier to get it right than to get it wrong.
Post reply on HN