3 ms·
There was no need for that "redesign". None. There is a distinct possibility that older Firefox could be in use today without issue. People must learn when to j
by OneDonOne 3y ago
There was no need for that "redesign". None. There is a distinct possibility that older Firefox could be in use today without issue. People must learn when to just leave certaon features alone.
- dblohm7 3y agoAs somebody who worked on the Gecko side on this, there absolutely was a need for a rewrite.
- OneDonOne 3y agoNot to sound like some sort of Pale Moon absolutist, but, I feel like the frontend changes were too much. And 3 years without Firefox biggest selling point is painful. It hurts. It really hurts. The only reason I haven't sold my soul and dignity to Chromium is that Iceraven lets me use μMatrix.
- dblohm7 3y agoIt had to be rewritten. Essentially there was no formal interface between the frontend and Gecko, and it had turned into a sluggish hairball of a monolith. We redesigned Gecko on Android to be embeddable (GeckoView[1]) and so a new frontend had to be written. That part was absolutely necessary. The rest of the debate is just about the UX, really. [1] https://geckoview.dev https://geckoview.dev
- dralley 3y agoIt wasn't just a "redesign", they replaced a significant chunk of the internals. And the new version is much faster and more responsive than the old version.