Mozilla's Plans For Firefox: More Partnerships, Better Add-ons, Faster Updates
An anonymous reader writes: Mozilla is reexamining and revamping the way it builds, communicates, and decides features for its browser. In short, big changes are coming to Firefox. Dave Camp, Firefox's director of engineering, sent out two lengthy emails, just three minutes apart: Three Pillars and Revisiting how we build Firefox. Both offer a lot more detail into what Mozilla is hoping to achieve.
I remember when a new version of firefox invoked excitement for what wonderful features they've added.
Now I just wonder what they've broken, redesigned or removed for no good reason this time.
This stuff they talk of is exactly why I don't use Firefox anymore. I don't want partnerships, and I don't want add-ons (okay, mayyybe one or two). A web browser displays the content... when it works properly, I should barely be able to notice the web browser is anything more than a window.
I honestly believe at this point, there's a group of people inside mozilla that are just going out of their way to destroy FF, the decisions have been braindead for the last 4 years.
Yeah, but reading your other posts it looks like you believe a lot of crazy shit.
The reality is that Firefox has been struggling figure out where to go next for years now. There have been some improvements to the core tech like the Javascript engine and HTML layout engine, but beyond that it was fairly feature complete long ago. There are some major architectural issues that need sorting (one process per tab, the add-on API, the plug-in API etc.) but those are hard to fix without breaking everything.
So they started to muck about with the GUI. If there's one thing that Slashdotters hate, it's GUI changes. Firefox was kind of a mess though, with two different menu systems (the Firefox button and the system menus), a preferences Window that reminds you of 1998 and IE6, lots of stuff that is only exposed via about:config etc.
Incompetent though the UX people at Mozilla may be, there is no evidence of malice here. Just not knowing what to do with a browser that has a lot of historical baggage in the code base that is blocking some of the real improvements people want to see.
const int one = 65536; (Silvermoon, Texture.cs)
SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC