As for yet another standardized API to replace it. As long as it provides the same functionality to all current services/devices that use RSS, that's fine with me. I would really prefer that it not be driven by Facebook and Twitter, however any more than I want Microsoft Office development teams driving the standardization of ODF.
Consider the case of a real-time news aggregator. A news source doesn't update very frequently (say once every 5 minutes), but you want to provide updates super fast (say within 30 seconds). That means on average you have to scrape the entire RSS feed 10 times for a single update. On the other hand, FB/Twitter APIs give you the flexibility to do things like "download items after this id," which hog much less bandwidth.
Rather, the slowness seems to come from the lack of an aggregation mechanism. If I want to follow 100 feeds (e.g. 100 Twitter users), I have to query each of those 100 feeds. Even though I can query them efficiently using If-Modified-Since, that's still slower than firing off one query to find out which of those 100 feeds have updates, and then querying only those which do.
Actually there is but twitter is not interested (for obvious reasons): http://ostatus.org/sites/default/files/ostatus-1.0-draft-2-s...
It's trivial to build an APP that generates an RSS stream for an arbitrary twitter account with their API, and I'm sure someone will soon. But the point is that they are setting a new standard for what can be done streams of structured data, and hopefully more sites will move away from RSS into cool APIs.
Of course, for now at least, there's no standard to this kind of API, but I think that people will eventually figure out what works and converge to it (as is the case with OAuth).