4 ms·

If 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-s

If 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 ago
But, 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 ago
But 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 ago
  Jitsi 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.
  - sml156 6y ago
    This is not a Firefox issue Quote from your link Nov 1, 2019 >we will soon start working on better Firefox support
    - rakoo 6y ago
      It's not a Firefox issue, it's an issue Jitsi has with Firefox which is the context of the parent comment
- XorNot 6y ago
  Yeah this is the sentence which jumped out at me too. Like, what? Across the diversity of new products out there, I've never had any problems with stuff not working on Firefox.
- robin_reala 6y ago
  I can, but it’s nearly always Google properties that are broken. E.g. the date picker in Google Books search was broken for a month up until a week ago. Oops.[1] [1] https://twitter.com/johnath/status/1116871251023278080 https://twitter.com/johnath/status/1116871251023278080
- codeflo 6y ago
  Just to be clear, Firefox is my main browser. Maybe we use different websites/webapps, but I run into more and more “optimized for Chrome” messages every year. There are lots of examples all over this discussion.
atomlib 6y ago
https://i.imgur.com/G20vFBJ.jpg https://i.imgur.com/G20vFBJ.jpg

npteljes 6y ago

But, 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 ago

But 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 ago
Jitsi 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.
- sml156 6y ago
  This is not a Firefox issue Quote from your link Nov 1, 2019 >we will soon start working on better Firefox support
  - rakoo 6y ago
    It's not a Firefox issue, it's an issue Jitsi has with Firefox which is the context of the parent comment
XorNot 6y ago
Yeah this is the sentence which jumped out at me too. Like, what? Across the diversity of new products out there, I've never had any problems with stuff not working on Firefox.
robin_reala 6y ago
I can, but it’s nearly always Google properties that are broken. E.g. the date picker in Google Books search was broken for a month up until a week ago. Oops.[1] [1] https://twitter.com/johnath/status/1116871251023278080 https://twitter.com/johnath/status/1116871251023278080
codeflo 6y ago
Just to be clear, Firefox is my main browser. Maybe we use different websites/webapps, but I run into more and more “optimized for Chrome” messages every year. There are lots of examples all over this discussion.

atomlib 6y ago

https://i.imgur.com/G20vFBJ.jpg https://i.imgur.com/G20vFBJ.jpg