Slash Boxes

SoylentNews is people

SoylentNews is powered by your submissions, so send in your scoop. Only 16 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: 2, Insightful) by Anonymous Coward on Thursday August 13 2020, @01:59PM (1 child)

    by Anonymous Coward on Thursday August 13 2020, @01:59PM (#1036130)

    Still, you often need someone else to show you what you wrote instead of seeing what you meant to write.

    I don't know about you, but it is really easy for me to read code as how I imagine I wrote it instead of how it is.

    Starting Score:    0  points
    Moderation   +2  
       Insightful=2, Total=2
    Extra 'Insightful' Modifier   0  

    Total Score:   2  
  • (Score: 3, Interesting) by barbara hudson on Thursday August 13 2020, @02:38PM

    by barbara hudson (6443) <> on Thursday August 13 2020, @02:38PM (#1036149) Journal

    Sure, which is why you have to keep going over it until you figure out where you screwed up. Handing that job over to someone else does nothing to improve either your debugging skills or your coding skills. Sometimes the best thing to do is put it aside for a day and approach it with fresh eyes and a fresh mind.

    It might be inefficient at first, because it would be quicker to give it to someone else, but in the long run, you broke it, you fix it is cheaper.

    People learn from their mistakes. Do something right 100 times, you learned nothing. Do it wrong once and fix it, you learned something. Have someone else fix it, what have you learned?

    SoylentNews is social media. Says so right in the slogan. Soylentnews is people, not tech.