I just want Firefox to be faster. I'm donating to Floorp (a Firefox fork), at least they seem focused on making the browser better.
Like, in general, I find that any HN thread where most of the comments are just agreeing, one-upping and yes-anding while invoking the same talking points and terminology (CEO ghouls, etc.) is probably a topic we might need to chill out on.
Mozilla makes mistakes just like any organization but they’ve done and continue to do more for an open Internet than most.
I know Mozilla does worse on benchmarks, but I never complain about performance. Recently I tried some sites from one of the spammiest sectors on the web and found I couldn’t move the mouse without my Chrome lighting up like a Christmas tree and navigating me to crap sites, but the Firefox experience was that I had to click on something for all hell break loose.
We have an internal app that has screen with a JavaScript table thingie with 40,000 rows loaded locally. Crazy? Yeah. It performs great on Chrome and lags pretty bad on the fox. That’s the only bad screen, and we have a lot of screens.
Personally I don’t like it that they have an office in San Francisco. Emotionally I think, “the only thing anybody should be building in San Francisco is a homeless shelter.” Practically though, I think a browser company can’t “think different” if is steeped in the Bay Area culture, not least if they can get in a car and go visit people at Google and Facebook. If they were someplace else they might have a little more empathy for users.
Read over the various web platform blogs out there, and keep a tally of how many times you'll see "Firefox gains support for XYZ in 139, bringing it to widespread availability. Chrome has supported this since 32 and Safari since version 16"
And many of these are fantastically useful features. Sure, they're not ground breaking building blocks like in the old days when IE didn't even support certain types of box model, but they're echos of the past
Component level CSS is simple enough that I didn't really have to go out of my way to do anything above and beyond, and if I had to I could just use a loader that uses sass or postcss or something similar, but it was a bit surprising.
That said, I have really enjoyed Lit. I wrote the original components for this project in 2023, and haven't really touched them till earlier this week. Bumped all package dependencies, and did the usual things you'd do for an upgrade, and they have had a stable API over the two years they've existed.
Regarding Dialog, a few years ago, when it was brand new, I was working on a project that used LiveView and SurfaceUI. We had a few modals that were used throughout the app, and I was in the process of migrating them to use Dialog before getting laid off. The tricky part, at the time, was that a Dialog invoked through pure HTML, no JS, lacked certain features that were available to the JS APIs. The HTML side has caught up, and the JS APIs have improved, but I've not touched frontend professionally in that time.