[josteink]

At this point, it seems like working with Google technologies (like Chrome and reader) is turning more into doing a uphill battle where you have to hack your way to an end, as opposed to just doing what you want.

At that point, why not just use something open and welcoming instead?

[platinum1]

How is being able to fork an open source extension to an open source web browser an "uphill battle" and not "open and welcoming?"

[josteink]

Currently Chrome is not an open-source browser. Chromium is.

As for Chrome, unless you are willing to go through hoops, it is only willing to install extensions from the Chrome Web Store.

You are now jumping through hoops to reinstall something you had installed which Google removed from their web-store.

Now Google which is your application (Chrome) and service (Reader)-provider, is working against you instead of enabling you. It didn't use to be that way, but now Google has changed.

That's the uphill battle. That's the not enabling part. That's the not open and welcoming. Contrast that to for instance Firefox and you will find a completely different picture.

Firefox has no mixed interests here, and that means they wont pull moves like this.