4 ms·

LOL, I love how people love to say what Mozilla _should_ do but clearly have no fuckin clue what goes on in that place.

• bulbar 2mo ago
  People seem to underestimate what a (even somewhat) large codebase entails. Even switching the compiler version is serious effort. Replacing the compiler can already be unfeasible, but apparently, switching the whole language seems to be super simple from the outside.
  • hn_submit 2mo ago
    Simple it ain't, but it's certainly doable if you have hundreds of developers working on it. It will reduce maintenance further down the line especially as far as vulnerabilities are concerned.
    • phyzix5761 2mo ago
      Hundreds of developers? Have you ever written professional software? There is no way a coordinated effort across hundreds of engineers is going to be efficient enough to do a port like this. Also, with most legacy software you can't port modules to test if your port is working. It becomes, mostly, an all-or-nothing kind of thing and with 25 million lines of code that's going to take a huge amount of effort and time.
      • hn_submit 2mo ago
        Yes, I've worked on software projects with large numbers of developers. And it's feasible if the work is split up in independent projects that only require the API to be agreed on. Exactly the type of work seen in a web browser, which has many interconnected but independent parts. I also believe that if you have enough unit test coverage you can tackle any project, no matter how large. This is, however, lacking in most projects. Many only pay lip service to unit testing.
• hn_submit 2mo ago
  Then maybe I should tell them what they shouldn't do: waste their money on management and other projects not directly related to improving the Firefox browser.