71–80 of 101 posts
Earlier quoted context omitted.
WebGPU is fairly recent and WebUSB is in the category of “why would I ever want my browser to access USB”, for me.
Both aren't supported by FF, and I can remember of other examples, that for all practical purposes make Chrome the new IE.
Chrome is open source and on mobile in the US is close to 50%.
There are similarities, but it’s far from the same situation.
Must join the choir and say that eventhough I have been a die hard FF fan, its gotten to the point of an impending divorce if performance doesn’t get better. I find myself switching to chromium more and more often. And then there are the extensions, that I sometimes can’t find for Firefox. That’s a minor annoyance than anything else though. There are also a bunch of things that keeps me with FF. multi container tabs…
Firefox has been faster than Chrome for many years now.
Earlier quoted context omitted.
That is not true, two harmful environments does not make either one a saviour, they are simply making web development worse.
Sorry to break it to you, without Apple, Google would have won already. Doesn't matter how good or evil they happen to be. No one cares about Firefox, apparently not even the large majority of HN folks.
Apple is as bad for the web as Google. They refuse to allow other engines on their mobile, money-making OS.
Earlier quoted context omitted.
Try to use WebUSB or WebGPU on Firefox.
WebGPU is fairly recent and WebUSB is in the category of “why would I ever want my browser to access USB”, for me.
With ESPHome[1] I could edit, compile and up upload firmware to my ESP device directly in my browser without installing any tools.
I had planned on using VSCode, but I got some extension conflicts due to some other extension (Platform.io IIRC).
I had the similar reaction when first reading about WebUSB as you, but after seeing how smooth it was, I admit I thought it was pretty darn neat. It drastically lowers the barrier of entry for those who aren't that technical.
[1]: https://esphome.io/
Earlier quoted context omitted.
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 don't see how that makes sense. Writing an API is less work than writing the devtools (which needs some kind of API anyway internally). So without a universal API, any serious new browser would take more effort to build.
aka How to tell that you don't design APIs without telling that you don't design APIs.
Earlier quoted context omitted.
--no-remote seems to have no effect -P asks me to select a profile. That's not what I want. I simply want a new Firefox window.
You may need to combine them like "Firefox --no-remote -P myotherprofile
I just want Firefox to launch a new window. No matter if there already are Firefox windows active or not.
Chromium has no problem doing so. So that is the reason I use Chromium and not Firefox.
Earlier quoted context omitted.
There’s no way to simplify web standards without breaking existing websites.
Websites should be built based on widely accepted standards, not quirks or monoculture 'standards'. When there were legally enforced browser ballots they had to ... and they did.
But I disagree that we shouldn’t also try to accommodate quirks. That’s why we have `Array.flat` instead of `Array.flatten` — the standards body decided to come up with a slightly atypical name for the feature rather than breaking a bunch of websites.[1] Our collective history is too valuable for us to be breaking stuff just to make engineers’ lives easier.