Mitch Wagner logo Mitch Wagner

Google bungled by killing Google Reader to build Google+, and then bungled again killing Google+ The company is like the proverbial donkey placed between a pile of hay and a bucket of water that ends up dying of hunger and thirst because it can’t decide between them.

How Google Reader died — and why the web misses it more than ever. By David Pierce at The Verge

Ten years after its untimely death, the team that built the much-beloved feed reader reflects on what went wrong and what could have been.

Google Reader was more than just an RSS reader. It was a general-purpose information hub and sharing platform. It achieved 30 million loyal users—a great success by real-world measures, but not Google scale.

Google’s bad reputation for killing and abandoning products started with Reader and has only gotten worse over time. But the real tragedy of Reader was that it had all the signs of being something big, and Google just couldn’t see it. Desperate to play catch-up to Facebook and Twitter, the company shut down one of its most prescient projects; you can see in Reader shades of everything from Twitter to the newsletter boom to the rising social web. To executives, Google Reader may have seemed like a humble feed aggregator built on boring technology. But for users, it was a way of organizing the internet, for making sense of the web, for collecting all the things you care about no matter its location or type, and helping you make the most of it.

Instead of building on Google Reader, Google wanted to build Google+, and look how that turned out.

I used Reader daily, but never got into the social features. I was barely aware they existed. I thought Google+ was great.

I also talked with ChatGPT. I asked it whether AI is a threat to people’s jobs, and how people can maximize their success in their careers as AI becomes more prevalent. I didn’t include ChatGPT’s responses in the article. Read them here.

My latest: Surviving the AI job apocalypse. AI won’t kill the human race or take everybody’s job. But the workplace will be transformed, and some jobs are at risk. Workers are already starting to adapt.

I recently came across the IndieWeb concept of POSSE. Not the first time I’ve seen it, but this time I read it more closely and said, “Holy cow, there’s a name for the way I’ve always preferred to use social media?”

It should be called “POSCE”—“Publish on your Own Site, Copy Elsewhere.” It’s a more understandable explanation of the concept. Though understandability isn’t a great strength for the IndieWeb movement.

I’m fiddling with my RSS/read-it-later setup—again!

This is an area I’m never satisfied with, and I seem to fiddle with it every few months. I find Inoreader is a mixed bag as a reading environment, though I’m continuing to use it because it’s unparalleled for filtering massive numbers of RSS feeds to find a few details that I need for my work.

So I’m experimenting with moving more over to newsletters, and then comes the question of what’s the ideal tool for reading newsletters. Inoreader? Matter?? Readwise Reader

I’m finding, to my surprise, that the ideal tool for reading newsletters may be … wait for it … email.

I do not share the general Mac power-user enthusiasm for tools that parse articles to strip out ads and make everything look the same. I find they introduce enough problems that they’re not hugely superior to the originals.