That’s all fine and good but Firefox on Android is currently in a sorry state. No per-site process isolation, buggy, can’t keep tabs open, slow, choppy, drains battery. Had to uninstall it on my brand new Galaxy S24+ and my Pixel 6 Pro because it was draining so much battery. When are you going to finally stop ignoring Firefox Android, Mozilla?
slow, choppy, drains battery
Sounds like you don’t have an adblocker.
I’m experiencing a similar issue on my phone and I’m using ublock, it is draining the battery very fast and making the phone hot.
I wonder if there is a good alternative/degoogled chrome for Android?
There is this.
Nope. He’s right. There are similar threads on reddit too every single week about the mobile version. It’s simply bad.
Maybe some issue with rendering on specific hardware…?
tab grouping
Sure, okay.
vertical tabs
To each their own.
profile management
Whatever, it’s fine.
and local AI features
HOLLUP
Focus on “local”. Mozilla is working since a while on that.
If you’re here because of the AI headline, this is important to read.
We’re looking at how we can use local, on-device AI models – i.e., more private – to enhance your browsing experience further. One feature we’re starting with next quarter is AI-generated alt-text for images inserted into PDFs, which makes it more accessible to visually impaired users and people with learning disabilities.
They are implementing AI how it should be. Don’t let all the shitty companies blind you to the fact what we call AI has positive sides.
They are implementing AI how it should be.
The term is so overused and abused that I’m not clear what they’re even promising. Are they localizing a LLM? Are they providing some kind of very fancy macroing? Are they linking up with ChatGPT somehow or integrating with Co-pilot? There’s no way to tell from the verbage.
And that’s not even really Mozilla’s fault. It’s just how the term AI can mean anything from “overhyped javascript” to “multi-billion dollar datacenter full of fake Scarlett Johansson voice patterns”.
there are language models that are quite feasible to run locally for easier tasks like this. “local” rules out both ChatGPT and Co-pilot since those models are enormous. AI generally means machine learned neural networks these days, even if a pile of if-else used to pass in the past.
not sure how they’re going to handle low-resource machines, but as far as AI integrations go this one is rather tame
AI generally means machine learned neural networks these days
Right, but a neural network traditionally rules out using a single local machine. Hell, we have entire chip architecture that revolves around neural net optimization. I can’t imagine needing that kind of configuration for my internet browser.
not sure how they’re going to handle low-resource machines
One of the perks of Firefox is its relative thinness. Chrome was a shameless resource hog even in its best days, and IE wasn’t any better. Do I really want Firefox chewing hundreds of MB of memory so it can… what? Simulate a 600 processor cluster doing weird finger art?
i mean, i’ve worked in neural networks for embedded systems, and it’s definitely possible. i share you skepticism about overhead, but i’ll eat my shoes if it isn’t opt in
I don’t doubt it’s possible. I’m just not sure how it would be useful.
I want fewer built-in features, not more of them. All of these things should be extensions, not built into the browser core.
I mean, I’d be perfectly happy for said extensions and more to be shipped by default – it would be good for Firefox to come “batteries included” even with adblocking and such, and that’s most likely the way I would use it. But I just want it to be modular and removable as a matter of principle.
I remember how monolithic Mozilla SeaMonkey got too top-heavy and forced Mozilla to start over more-or-less from scratch with
PhoenixFirebirdFirefox, and I want it to stick close to those roots so they don’t have to do it again.They are probably extensions, just like pip, pocket, screenshot upload, languages, search engines, themes, etc.
Shipped by default, handled like extensions internally but not exposed to the user. You see it in the extension*.json files in your profile folder.
In that case, I want them exposed just like user-installed extensions, so it’s more obvious how to get rid of them if you want.
Yeah, me too. I made once a pacman hook that empties the respective folder in /usr on update/install. I have no use for all of them and picture-in-picture is annoying to me.
Btw, i think it’s mentioned somewhere in about:support too?
Tab grouping, nice! Finally back after they removed then years ago…
