704
Mozilla is adding tab grouping, vertical tabs, profile management, and local AI features to Firefox
(connect.mozilla.org)
this post was submitted on 23 May 2024
704 points (99.0% liked)
Technology
59157 readers
3239 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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 ~~Phoenix~~ ~~Firebird~~ Firefox, 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?
We need modular browsers. It is hard for Mozilla to keep the track to the W3C and all the nonstandard stuff that Google, Microsoft and Apple add to their browsers. If those elements were modules, it would be easier for people to collaborate and for Google and Microsoft to be obligated to add support for other browsers.
You're talking about a modular rendering engine, which is a different thing than what I'm talking about. I'm talking about stripping down the UI until it resembles XUL Runner, then adding the functionality back as extensions.
You're not wrong that it's important for the engine's code to be organized well for developers' benefit (and ideally for the engine as a whole to be self-contained -- it'd be great if Gecko were as easily-embeddable as Blink), but I'm not so sure that users need to be able to add or remove pieces of it in a way similar to what I'm talking about for UI features.
More concretely:
I think Firefox should ship by default with all the functionality it currently has, plus uBlock Origin and some other things. But I want it to be designed such that if you went into the extensions manager and disabled everything, things like tab support, bookmarks, history, and maybe even the address bar and back button would be gone. It would still be capable of fully rendering a web page, though.
If they do that, normies will start yelling that Firefox has removed their beloved features and will immediately download Chrome. I have a strong suspicion that a majority of people don't use extensions at all.
Did you miss this part of my previous comment?
Okay. Replace core features as extensions. Kind of like the suckless philosophy.
While it's a good idea, I think extensions are purposefully made weaker, that is, they don't/can't have the same capabilities of core features. It will require a huge rework which I just don't see happening.
The default experience when people Google "install Firefox" should absolutely provide as much feature parity with other major browsers as possible. 99% of users will want them or not mind them. And for that last 1%, I guess I'm not sure if it's worth the development headaches for them to bake in a configuration change that power users could get by forking the codebase anyway.
Something like a deeper integration of an addOn/extension would be nice.
Modularity could be a way to do it.