4 ms·
About ~70 people are impacted, mostly platform engineers. That means that they are getting rid of ~10% of their engineering, including Gecko module owners and p
by fabrice_d 9y ago
About ~70 people are impacted, mostly platform engineers. That means that they are getting rid of ~10% of their engineering, including Gecko module owners and people with very hard to find skills. But they keep failed VPs on the payroll.
Of course they give no explanation, because MoCo leadership is one of the worse you can think of, with their actions in total contradiction with their PR. They are betraying their own employees, and the Mozilla community at large.
After spending a year claiming that they were back with a rebuilt web runtime, they do that...
RIP Gecko
- acqq 9y agoLooking who was fixing bugs in the "Core" of Firefox, there were a lot of Chinese names. It seems that's "the Taiwan office" mentioned, and it also seems Mozilla executives killed exactly those who improved the browser day to day. Nobody should believe the PR -- even with the latest "new" stuff added it's still the "old" stuff that has to be improved as the "new" stuff is still just the "leaves" of the whole "tree." Firefox still eats significantly more battery than any other browser during typical browsing sessions.
- pcwalton 9y ago> Nobody should believe the PR -- even with the latest "new" stuff added it's still the "old" stuff that has to be improved as the "new" stuff is still just the "leaves" of the whole "tree." The Servo CSS style system, which was practically the headline feature of Quantum, is about as far from the "leaves of the tree" as you can get. Claims like yours are kind of insulting to those of us who worked really hard on it, to be honest.
- acqq 9y agoThe old infrastructure is still big and it dominates that what eventually makes the browser. Don't react with "being insulted" when there are techical claims that are either true or not. When Firefox takes twice as much power than other browsers all the time while displaying the whole page, it's because Gecko works as it works. The new code is excuted on some occasions in the "leaves" posituon of the code trace "trees" and still hasn't made Firefox less power hungry. Any other browser is better in that regard, and that is an actual sad state of Firefox. Sacking those who were supposed to work on such issues is a crazy management decision. The ladt time I've checked, Servo is a project that is not inside if the Firefox/Gecko but only contributes some pieces to it. So what's your problem again?