But enough where my app supports both and will support both for the remainder of time!

And enough to bifurcate the community by having two conflicting standards!

Is it really bifurcated for the end user though? Its the same tooling to view both feeds. The same workflow to add either feed to your feed reader. You don't even realize whether its an atom or rss feed unless you start looking into it.

> Is it really bifurcated for the end user though?

Yes. Suppose you are build feeds search engine. User enters query that matches some blog. This blog exposes both RSS and ATOM feeds (very common scenario). Which one should your engine show in the results? If it shows both, which one the user should select for reading? And what if they differ, but only slightly? Why should the user be exposed to that?

It's certainly a bifurcation for feed authors.

Just pick your favourite and supply that? If all consumer software supports both formats, why do you need to provide both?

Who's relying on one, who's relying on the other? Dunno! I guess we'll support both, because we're good Internet citizens that believe that breaking links is the absolute worst thing you can do.