1,771 karma · joined December 8, 2007
Is an interesting thought experiment. In one stroke Google could wipe out a large tent pole for the RSS eco system. Wouldn't that effectively make RSS dead?
Not only do people use Google Reader as means to read RSS, way to many RSS Readers use Google Reader as the crawling infrastructure for there app.(Newsblur being a notable exception). So killing google reader would pwn a large number of apps.
After the main support is gone, why would you build RSS into your product at all? Can RSS, that is propped up by one tenuous pole, last forever?
Fat arrow is well understood in the JS community because of CoffeeScript, and that is one reason why people are pushing for fat arrow to be accepted. I personally think CoffeeScripts has had a very large impact on the idea.
I don't think that was what the article was about, but I think that bare statement,"Your identity ≠ Your code", is wrong.
Making UI open source helps everyone.
http://www.rumproarious.com/2012/01/31/rss-needs-a-new-pr-te...
If you accept that premise, you are building a product for informed, longish-term computer users, and you are treating them like they are beginners. If my intrest was piqued by RSS I probably already use an RSS reader, and have a bunch of feeds I want to use.
You are missing the ability for me to organize my feeds into folders. I have a lot of feeds, and I need folders to triage my reading into a sliding scale from important to least important.
After all of this keep it up, because I am, and I think many others are, willing to pay for an app that does RSS reading well.
What is broken though is they don't seem to support folders.
The root issue here is that the developer assumed how somethig worked, and didnt bother to learn how it actually worked.
I actually do have issues with data attribute for this exact reason, but that is no excuse for not looking up how it actually works.
http://alexkessinger.net/2010/12/17/doing-a-pixel-ping-witho...