So, my personal blog doesn't get a ton of traffic, but the one article that gets the most traffic is an article about how to monkeypatch feedparser to not strip about embedded videos.
While not hard evidence, I think it's indicative of the kind of experience a developer has when they choose to engage with syndication.
Human misery isn't something most companies want to be associated with. For that reason, many companies don't want their ads to run next to content like that. I've personally had to quickly pull ads off a site because of that fact.
We spend far more time consuming content generated by our friends and family then we do consuming content created by media companies. I don't think he could conceive that a company like Facebook could control the means of distribution by providing something that people want more the professional media.
Webdis has more features right now. It has authentication, and it supports things like websockets. It's also written in C.
Lark is written in python and I would argue that Lark does a better job of meeting the expectations of what an API should be like supporting POSTs, and DELETEs.
It would also fit in well with an existing flask project. It has a blueprint that you can mount.
oAuth integration is planned, I am working on it right now. I also plan on making websockets work in the same manner as flask-sockets.
Content owners don't make feed readers. If they didn't want people to pre-screen content they could just get rid of their RSS feeds altogether. They haven't done that. They clearly find some value to users being able to find their content through RSS, so I don't think this is why feed readers have failed to breakout.
It's not just your tools though. They are asking you to throw away many of your ideas about web development as well. They ask you to adopt a new paradigm that doesn't fit in with the template, innerHTML style of development.
If you embrace that idea, and go with the flow, you can do some amazing things amazingly fast with angular that doesn't work so well in other frameworks.
Out of all the feeds that I checked CNN had the largest number of Google Reader subscribers. If you are right, I would argue that CNN market penetration is lower then 50% and thus the feed reader market would be bigger.
You aren't alone. There is actually a version of Markdown for writing Screenplays. When writers adopt Markdown then I am not sure who Markdown is not for.
http://octopress.org/ is essentially something written from the ground up that addresses many of the concerns in ghost, but that doesn't mean its the solution.
Because WordPress is built on PHP it has a wider array of deployment options, including many low-cost options, while maintaing a relatively easy to use sheen.
I think it makes sense to evolve WordPress to merge the benefits of something like octopress with WP.
What made sense about the Ghost write screen was that it embraced Markdown. It showed what things would look like as you wrote them. I don't think the screenshot of the new WordPress dashboard addresses that.