To refute your last point, the article explicitly mentions that that Twitter has functional RSS support, which was deliberately removed from the user interface and metadata, so it's not a matter of development or maintenance cost.
"The demise of RSS"
"The downfall of RSS"
Or if you want to get superdramatic: "The silent acquiescence of RSS to an untimely demise"
It’s not a war. Not even using extremely liberal (and stupid) definitions of war.
Mechanical fish is right, RSS is unattractive to people, that is the problem. People don't hate it, it isn't a war.
<link rel="alternate" type="application/rss+xml" href="...">
pointing to a URL that already exists and works just fine doesn't cost anything. If the primary reason had been maintenance cost, they would have removed the feature itself.
The next step, in many cases, is to send out sorrow-filled notices to the feature's users saying, in essence, that you're end-of-lifing the feature as of date X. Though often the bad news is artfully disguised. (e.g. "Look at all the glorious new stuff that we're rolling out to replace that tired old feature that will now be deprecated and slated for removal.")
Only in step three do you just shut it off. You might even shut it off gradually, as when Google shut off their old design for Gmail, a process which is still going on and appears to be taking literally years.
How much time elapses between the three steps depends on the details.
(Please, please refute me: Tell me a good iOS feed-reader that syncs my read status between my iPhone and iPad, but doesn't require me to use Google Reader.)
Google may not technically own RSS, just as they don't technically own Android, but they own Google Reader and Feedburner. Maybe that's not a mousetrap, strictly speaking. But I still feel stuck.
Have you tried Newsblur (http://www.newsblur.com/) - has a great web app and complementary iPhone app. Samuel Clay (the developer) is often on HN too, although his username escapes me right now.
On an individual level, Google Reader used to be like crack for me, I couldn't get away from it. Used it every day. Followed hundereds of websites. Then the tore the social out of it and clunklily put it into G+, which blows (no reader user liked this). Now I almost never use google reader. It's almost like they were trying to push people away from it. But that's just my two cents.
http://www.theatlanticwire.com/technology/2011/10/sharebros-...
But progress has fizzled to nothing:
"I'm also usually very open to change and what have you, but I despise the new reader. Exactly because I like to be in reader, and see what my friends posted from reader. I don't want it mixed with the rest of my social life, I don't want it mixed with FB like status updates, I just want to see what people are sharing in Reader. It's like I had my own "community" in reader, a small but special subset of people really in the "know". Yeahyeah, that's a circle, I know, but I went to reader to read what they shared, then I read my own, and shared. The 'dialog' was more circular, if that makes any sense. That, and my Reader slants heavily on the 'images' and artsy side of things, it was almost like a micro tumblr that only friends saw, but unlike tumblr, it's not recycled stuff, we are all pulling from different places, I followed a guy from finance, a dude that loved astronomy, and chick in advertising, a guy in tech, a girl into silly comics, and it was all right there, im my reader. It was perfect."
http://www.thedailyshow.com/full-episodes/mon-april-16-2012-...
around 7:00.
Has anyone?
My impression is that we have the opposite of a "war" here. These RSS features are dying of natural causes. Unless someone can point me to the conference, blog post, or secret meeting where an evangelist convinced Twitter, Facebook, Apple, Mozilla, et cetera to simultaneously kill this feature in tandem, I'll continue to suspect that they're doing so because they're all subject to the same market pressure: There's a lot of new, popular, paying features that need building, from Twitter and Facebook integration, to mobile apps, to mobile-friendly APIs, to responsive and touch-friendly design, and as these things get added to the backlog other things get pushed down. Code is expensive to maintain and if it doesn't carry its weight it gets cut, even if it's vaguely likeable and nifty.