Over the years I've gone back and forth, using RSS, then not using it, then using it again. I used to use the RSS reader in Trillian, but feed management was an issue, so I stopped. I returned again just after Reader was shuttered and used Feedly via Reeder for iOS. I couldn't get into it as much on the desktop. Now that I'm on Android, I use gReader, but it's all still Feedly under the hood. I do most of my RSS triage on my mobile in gReader, send articles related to work or that need further action to Instapaper, then pick them up on my desktop using that service. General news I just read on my mobile device.

Each situation is different, but sometimes slowing the user down can reduce errors/improve accuracy. It's not that the user experience is "too good," but moreso that certain UX and design decisions can make the outcome of an interaction less than desirable. Luke Wroblewski talks a bit about this in his book Web Form Design (Rosenfeld Media). He discusses the placement of labels with regard to fields and how each option affects completion in terms of speed and accuracy. O'Reilly also uses similar logic in the creation of their Head First series. They use Comic Sans (and other design tricks) to slow down the reading experience as studies have shown it aids with retention. There's nothing wrong with slowing a user down if it's in their best interest.

We were hoping ACID4 would come together under our leadership, but we could not get it to materialize.