Engineering code quality in Firefox
I am glad they are looking into this:<p>Sorry for the following rant, but I really don&#x27;t think of Firefox browser when I think of code quality. (Still don&#x27;t even though it has improved a lot in some areas).<p>When it comes to browsers, I still feel the old Opera browser (presto), that had more features, was blazing fast and small in size (in memory) is a very good example of a finely engineered software. In the early versions they really cared about optimizing for performance, using less memory and less power (on mobile devices) - I am amazed that years after, modern browsers are bloatier now than ever and just don&#x27;t seem to care as much about these aspect as much as Opera did.<p>Questions like how modular is Firefox, how easy is it to customize Firefox (add or remove feature from the code), how easy is it for someone to use the Gecko rendering engine in their own project etc. all kind of indicate the bloatier, messier nature of the code within Firefox (in my opinion).<p>It&#x27;s like browser developers now a days only care about adding more features (read bloat) without considering any constraints ...