Comment by Communitivity | Hacker News Reader

Comment by Communitivity | Hacker News Reader

The problem is that Google is removing services that are key to Chromium use for many users. I wouldn't consider this locking down, or removing services (though it is technically that). Instead I would consider it cutting Chromium off at the knees.

I suspect, but have no evidence, that this is in reaction to Microsoft basing the newest version of their browser on Chromium.

The solution is to use an Open Source browser, such as Firefox or some other alternative. That's going to require more developers though to pitch in and help get feature parity in their favorite Open Source browser.

I also have some concerns there, as the Firefox CEO Mitchell has said Mozilla tends to focus more on money. We've seen indicators of that recently with sponsored search. I remember the old AOL Browser and AOL Email, and the ads. I hope not, but could see Mozilla implementing ads in the Firefox UI area.

What I'd like to see is a browser that is built of swappable components working around a browser microkernel consisting of a web engine (Servo?), a JavaScript engine (Deno?), a plugin framework that works via messaging and can support various msg protocols (with two ref impls:ZeroMQ and Matrix). Think something like the Eclipse RCP, but for the Browser and Web browsing.

If this sounds interesting, send me a message. That's not an ad, I am interested in gauging the interest in a project like that.

> The problem is that Google is removing services

> The solution is to use an Open Source browser

Seems to me the solution is to use 3rd party services that are not tied to the browser at all.

For example I manage passwords with 1Password, not Chrome's or any other browser's sync services. And I use bookmarking services like Pocket which aren't tied to any browser.

Using independent services made by companies that care about their reputation (and therefore the quality of their product) makes a lot more sense to me then putting all your eggs into a single browser basket.

I agree, and I'd like to see a unified way of connecting to those services. These services are in a way plugins, so I could see it being handled by having a plugin framework that's capable of handling in-app plugins via something like ZeroMQ, as well as external plugins (remote services or from other apps) via something like Matrix.

Essentially, a key part of the idea is to create an Open Source project that is a browser construction kit rather than a browser. Then anyone can choose what components they use. Big brands can release branded sets of components that include proprietary components if they want - but users won't need to use those to have a safe, secure, and rich browsing experience.

> The solution is to use an Open Source browser, such as Firefox or some other alternative.

Serious question: Why is Chromium the default in any open source operating system? For all the talk about how Google has their own interests with regard to the web in general, and more specifically Chromium, why do Fedora/Arch/Mint/Raspbian (even Debian uses Firefox by default) include it as a default?

I realize you may not be equipped to answer this question directly, but I've been wondering this for some time, and the question seems germane to your point.

> I suspect, but have no evidence, that this is in reaction to Microsoft basing the newest version of their browser on Chromium.

I don't think it's this. As far as I'm aware, MS removed basically every Google integrated service from the new Edge before shipping it. They implemented their own profile syncing service, and I don't believe they support click to call anywhere (or at least they didn't when I last used the linux beta).

If Mozilla can't build a browser with a $60M/yr from Google and other funding, how can you can build one from scratch without funding?

With donated labor contributions from hundreds of engineers interested in an open web where users have privacy and control their own data and perhaps crowdfunding down the road. It's a big dream. Heck, maybe it's a pipe dream - but it's still a dream worth striving toward. Maybe I don't build the entire staircase, just a couple steps (Open Source browser building blocks others can run with). The next person then builds a few more and shores up the existing ones, the one after that does the same, and so on. Eventually you might just have a staircase. Servo is one of those steps. So is Deno.

Reply on news.ycombinator.com