34 ms·
>Specifically, it's not worth it if no one uses it because they've switched to Chrome to get the functionality they want. Agreed with the overall comments in c
by ksec 6y ago
>Specifically, it's not worth it if no one uses it because they've switched to Chrome to get the functionality they want.
Agreed with the overall comments in comment section. Seems like an overreaction or making a big deal out of nothing.
Am I missing something?
- kylebenzle 6y agoMaybe. I think this single action cements Google as a bad actor and pulls the "open source" rug out from under Chrome. This ONE thing will be the defining factor in me dumping Google moving forward.
- onethought 6y agoReally, couldn’t one that cared about this just add bookmark syncing to chromium? Using some other service?
- corty 6y agoOne could, but the Chromium sourcecode provided by Google is a quickly moving target. So your patch will need to be updated very often. Distro maintainers are already complaining about Chromium being a lot of work because of the rate of change and build breakage. A patch will make that worse. Also, I would bet Google would do a few "neccessary" changes in the bookmark parts over the next releases, just to make your patch not work.
- takluyver 6y agoThe specific problem of syncing bookmarks is probably solvable with an extension. But the move suggests that Google doesn't view Chromium as something that people will use directly, like they're not interested in people using open source Android without their proprietary components. If they gradually make more and more pieces Chrome-only, it will get harder to make a relevant browser by forking Chromium, because there will be more to reimplement before people consider using it. And, of course, that makes perfect sense for Google. Chrome is no longer the scrappy insurgent. It's the king of the hill now, so it can start putting the fences up against competitors.
- codeflo 6y agoIf running Chromium is no longer viable, and the web increasingly doesn’t work on Firefox, then for the first time in the web’s history, we don’t have an open-source browser. The web becomes proprietary tech owned by Google. Just let that sink in.
- npteljes 6y agoBut, what exactly do these APIs do that would make chromium , and open source browsing, "no longer viable"? A browser works perfectly fine without bookmark sync, and apparently that's the most painful API to remove.
- onethought 6y ago... or just like the last browser war that Firefox won.
- spijdar 6y agoBut all this really does is prevent some google services from working. Why does that make it "no longer viable"? I use both Firefox and Chromium on ppc64le because only Chromium has a working JIT compiler through IBM's V8 port. I don't use sync or any of Google's services, because I'm just not interested. Talking about dropping Chromium entirely over it feels like either an overreaction or a political move to try and get Google to acquiesce.
- paxys 6y ago> and the web increasingly doesn’t work on Firefox I have been using Firefox as my daily driver for years now and I can assure you the web works perfectly fine. I can't remember the last time I came across a website that was even slightly broken on Firefox and worked on Chrome.
- rakoo 6y agoJitsi has issues with Firefox (https://github.com/jitsi/jitsi-meet/issues/4758 https://github.com/jitsi/jitsi-meet/issues/4758) preventing it to work as well as in Chrome.