vord1080

Not sure where you got the idea that the core development team has been cut, Firefox development remains strong. For example, here's a 1,000+ line patch that just landed two days ago. https://bugzilla.mozilla.org/show_bug.cgi?id=1779952

Before turning this into another Mozilla hate thread, we should consider the following:

1) Mozilla China is practically an independent organization and their Firefox builds have been quite different from "Normal" Firefox for a long time.

2) That error code is 451, "Unavailable For Legal Reasons", usually used to indicate government censorship.

Under normal circumstances it would gracefully fail. If the connection fails normally the browser will keep trucking along, the problem was a bug deep inside the network stack that could've been triggered by any HTTP/3 connection.

Does this support Firefox?

average disingenuous HNer making comparisons between compilers and web browsers. Everyone involved knows Shadow DOM V0 was a rush job, as was the YouTube redesign that used it (it had major perf issues even in chrome when it came out). The standardized ShadowDOM v1 is better in every way and works in all browsers. It's pretty clear that Google wanted V0 to spread as far as possible so they could force it to become a standard, as removing it would "break the web". Shadow DOM, regardless of version, isn't critical for a product like YouTube. The "web" is only the "web" if parties involved play fair, even just a bit, otherwise it's back to IE6.

Works fine on Windows. Linux only makes up 3% of Firefox users so it's no surprise they haven't prioritized it.

That's extra strange. Because Firefox on iOS is just a thin wrapper over a WebKit Webview. It should basically be as stable as safari then.

> You would recoil in disgust.

Why would I recoil in disgust? What if I prefer ads to total dependence on a single revenue source?

Also comparing Brave to Firefox is like comparing a browser with it's owns independent stack to a browser that's just a fork of a different browser, wait!

> They certainly wouldn't have shitcanned the Servo project, really the only possible threat to Google's de facto monopoly over the web and the biggest meaningful way to fight for the open web.

Anyone that followed Servo closely knows it was a dead end. It was literally never going to ship, ever. They freaking started a rewrite of the layout component at some point. Simple pages like google.com kept breaking. It was an R&D project, the good stuff already got merged into gecko (Stylo, WebRender). A lot of top servo contributors and GFX people got moved to Gecko. The project fulfilled its purpose, it made Gecko better.

That's unfortunate, you should try updating your GPU drivers (if you're on linux there's some different things you need to change). Firefox uses the GPU for more stuff so bad drivers really heck it up.

Container tabs. Good text rendering. Support for some niche css features, the WebExtension implementation can support more advanced extensions (sidebar, runtime theme modification, dns, etc). shift+right click to bypass websites that block context menus. if a website uses the background-image css property, the firefox context menu will have the correct image options and chrome won't. i can hold ctrl and properly select HTML tables to paste into spreadsheets.

> But chrome's security and performance is miles better than firefox.

Not really. Maybe ~6 years ago but they've made insane progress. Full site isolation is rolling out now and the performance is great. Definitely faster than Chrome on my laptop.

You can turn on WebMidi by setting dom.webmidi.enabled to true in about:config, though that isn't a default so it's still a very valid criticism sadly.