CSS scroll drive animation (standard), Cross document view transitions (standard), CSS corner shape, Multicol Level 2 (standard), some of the Filesystem Access API, WebGPU on linux, PWA manifest install (standard), took 3 years to ship documentPictureInPicture.
Facts are facts. Web standard are implemented first in chromium, then in firefox after years.
what?
Chromium based browser have strict multiprocess isolation. This is not true for firefox. If a tab crashes chrome it does not crash the entire browser. This is only partially true for firefox
yes it is a known fact that google sites including youtube are engineered to be slower on firefox.
Yes, and if you check browser performance on a neutral benchmark like speedometer 3.1 chrome is still faster. Also this is a fact.
Chromium is an objectively slightly better browser on paper than Firefox. Firefox is a much better browser for your privacy, for open source development and the health of the web in general.
CSS scroll drive animation (standard), Cross document view transitions (standard), CSS corner shape, Multicol Level 2 (standard), some of the Filesystem Access API, WebGPU on linux, PWA manifest install (standard), took 3 years to ship documentPictureInPicture.
half of these are animations. are you choosing your browser by what cool animations it supports?
certain things are better unimplemented. like webusb and complete filesystem access, because they are too dangerous features to give to random websites by a single click. if a website wants to access arbitrary parts of my filesystem they should develop a downloadable app for that.
webgpu and pwa support are indeed happening slowly. Unfortunately firefox does not have as much funds as our favorite advertising supergiant does, and they are just the same plagued by a CEO who can’t ever be fulfilled with enough of a paycheck. you will not fix that by switching to chrome.
document picture in picture kind of sounds WTF, like the other feature allowing arbitrary HTML to he rendered onto a canvas. I feel it more with the latter, but sometimes I just feel google is intentionally making the web a standard too heavy to have competitors.
Web standard are implemented first in chromium, then in firefox after years.
I just addressed this in the previous sentence.
Chromium based browser have strict multiprocess isolation. This is not true for firefox. If a tab crashes chrome it does not crash the entire browser. This is only partially true for firefox
how is that only partially true on firefox? this is exactly the reason why it consumes so much memory when having lots of websites open.
I do not remember the last time firefox crashed for me. must have been many years ago.
Chromium is an objectively slightly better browser on paper than Firefox.
only if you completely ignore a bunch of aspects of it. in reality, it has a few advantages and lots of disadvantages. oh, and its also the default for billions of people who have no clue why choose one over the other.
CSS scroll drive animation (standard), Cross document view transitions (standard), CSS corner shape, Multicol Level 2 (standard), some of the Filesystem Access API, WebGPU on linux, PWA manifest install (standard), took 3 years to ship documentPictureInPicture.
Facts are facts. Web standard are implemented first in chromium, then in firefox after years.
Chromium based browser have strict multiprocess isolation. This is not true for firefox. If a tab crashes chrome it does not crash the entire browser. This is only partially true for firefox
Yes, and if you check browser performance on a neutral benchmark like speedometer 3.1 chrome is still faster. Also this is a fact.
Chromium is an objectively slightly better browser on paper than Firefox. Firefox is a much better browser for your privacy, for open source development and the health of the web in general.
half of these are animations. are you choosing your browser by what cool animations it supports?
certain things are better unimplemented. like webusb and complete filesystem access, because they are too dangerous features to give to random websites by a single click. if a website wants to access arbitrary parts of my filesystem they should develop a downloadable app for that.
webgpu and pwa support are indeed happening slowly. Unfortunately firefox does not have as much funds as our favorite advertising supergiant does, and they are just the same plagued by a CEO who can’t ever be fulfilled with enough of a paycheck. you will not fix that by switching to chrome.
document picture in picture kind of sounds WTF, like the other feature allowing arbitrary HTML to he rendered onto a canvas. I feel it more with the latter, but sometimes I just feel google is intentionally making the web a standard too heavy to have competitors.
I just addressed this in the previous sentence.
how is that only partially true on firefox? this is exactly the reason why it consumes so much memory when having lots of websites open.
I do not remember the last time firefox crashed for me. must have been many years ago.
only if you completely ignore a bunch of aspects of it. in reality, it has a few advantages and lots of disadvantages. oh, and its also the default for billions of people who have no clue why choose one over the other.