Slash Boxes

SoylentNews is people

SoylentNews is powered by your submissions, so send in your scoop. Only 15 submissions in the queue.
posted by chromas on Thursday August 13 2020, @05:55AM   Printer-friendly
from the here-today,-gone-tomorrow dept.

Mozilla lays off 250 employees while it refocuses on commercial products

The Mozilla Corporation announced today it was laying off approximately 250 staff members in a move to shore up the organization's financial future.

The layoffs were publicly announced in a blog post today. Employees were notified hours before, earlier this morning, via an email [PDF] sent by Mitchell Baker, Mozilla Corporation CEO and Mozilla Foundation Chairwoman.

Baker's message cited the organization's need to adapt its finances to a post-COVID-19 world and re-focus the organization on new commercial services.

[...] In 2018, the Mozilla Corporation said it had around 1,000 full-time employees worldwide. Mozilla previously laid off 70 employees in January. Several sources have told ZDNet that the recent layoffs accounted for nearly a quarter of the organization's workforce.

Main casualties of today's layoffs were the developers working on the company's experimental Servo browser engine and Mozilla's threat management security team. The latter is the security team that investigates security reports and performs incident response. The security team that fixes bugs in Mozilla products is still in place, according to sources and a Mozilla spokesperson.

Changing World, Changing Mozilla


Also at TechCrunch and The Verge.

Original Submission

This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 1, Informative) by Anonymous Coward on Friday August 14 2020, @06:39PM

    by Anonymous Coward on Friday August 14 2020, @06:39PM (#1036654)

    It was originally an independent project to strip off the bloat of using javascript and html/xml markup to generate the user interface running on top of... either gtk 1.x or very early 2.x in order to have cross platform compatibility. It was fast with a small memory footprint, and the initial source of tabs on Netscape/Mozilla Browser (they were still using the browser window paradigm where each open page was its own window).

    The switch to XUL happened after the project had become popular and they offered the developer a job, before moving someone else in to manage the project, then start pushing the XUL crap on firefox as well (( think they started with the interpreted garbage that had made the post-Mozilla browser suite so slow, but were working on the JIT javascript support around that time.) End result was the customizable and plugin friendly Firefox that we all accidentally pitched to our friends because most of us were still using the native widget client with none of the XUL overhead. Then systems jumped up in memory and cpu performance during the late p4/athlon xp and early core2/athlon64 era and most of the people who hated xul finally switched because there wasn't a compelling reason not to. As an aside: If i remember correctly, there were a lot of xul related exploits during that time, which firefox avoided, while general javascript/media handling exploits worked on both, but generally didn't get as far on firefox. XUL changed all that for the worse.

    Starting Score:    0  points
    Moderation   +1  
       Informative=1, Total=1
    Extra 'Informative' Modifier   0  

    Total Score:   1