21–30 of 101 posts
Earlier quoted context omitted.
Are you comfortable handing Google the power to dictate the future of the Internet?
It's the customers handing power to google, not the devs.
Many of whom only care about Safari, because contrary to Firefox, Apple gets to say Chrome doesn't own their platforms.
Earlier quoted context omitted.
Browsers are so similar these days, web standards are so well defined, I see little reason to code Chrome-only sites. Having been through the IEs of the 90s/00s, I feel proud that we managed to scape what seemed an irreversible fate and a sense of responsibility to do whatever I can to help prevent it from happening again.
Try to use WebUSB or WebGPU on Firefox.
Why isn't there an API for writing devtools, so that we can have some more competition in this space?
To have more competition in web devtools, we need to simplify the web standard so more browser can appear instead of forcing some new fancy API on our almost monopoly.
Can you modify and resend a request in Chrome yet?
Earlier quoted context omitted.
Try to use WebUSB or WebGPU on Firefox.
I’m not sure about WebGPU, but WebUSB was pushed through by Google without any regard at all for Mozilla’s and Apple’s concerns, so it’s not too surprising it’s a Chrome exclusive.
Thanks to Chrome worshipping, there is no Web anymore, Apple is the only wall preventing Web developers to replace Web with ChromeOS on their CV.
Earlier quoted context omitted.
It’s both, however, developers have a disproportional amount of power to tip the balance.
Yep. The only reason why Firefox, Safari, and eventually Chrome were able topple IE is because devs started writing predominantly for those browsers. Without that push IE would’ve lived on, because users don’t switch that kind of thing unless they really have to. Devs often also have disproportionate sway over the technical choices of friends and family, which is where Firefox got much of its footing earlier on.
Meanwhile, devs were still targeting IE because it was where the users were. It was totally preferable to develop for Chrome or Firefox, but I recall spending countless hours still getting that stuff to IE, because that's what customers were using.
Sure, developers helped speed along adoption, but I think the new browsers ultimately succeeded because they're better products for the customer.
Why isn't there an API for writing devtools, so that we can have some more competition in this space?
We need less API/standard, not more. To have more competition in web devtools, we need to simplify the web standard so more browser can appear instead of forcing some new fancy API on our almost monopoly.
I develop, test, and debug on browsers that my users are using, and that ain't Firefox.
For some reason, new Firefox windows can only be launched from the same environment from which the first window has been started. Even the same user who started FF cannot launch a new window from a new shell. That constantly interferes with my workflow. Example: Say firefox has been started from the Destop already and now I want to start a new Firefox window from a root terminal: su desktopuser firefox It does not wo…