1. 91
  1.  

  2. 14

    I’m wondering what this means for Mozilla’s priorities. Are they no longer interested in Servo’s goals, or has the project just reached enough maturity that it can live on outside of Mozilla?

    1. 26

      Mozilla laid off the Servo team. Some of the libraries that came out of Servo like the CSS engine are also used in Firefox, and those parts will likely see continued development support from Mozilla. Mozilla is no longer working on Servo itself - the completely packaged browser engine.

      1. 9

        Probably the latter. Servo was always a test bed for new implementations of web technologies, which they slowly merge into the main browser, library by library.

        The Linux Foundation announcement (while otherwise worse), also lists a number of additional stakeholders: “Industry support for this move is coming from Futurewei, Let’s Encrypt, Mozilla, Samsung, and Three.js, among others.”

      2. 9

        I really wish they could secure some EU funding. That really makes sense, from competition point of view(in the European meaning).

        1. 3

          Not under a US umbrella foundation.

        2. 9

          Yeah, I’ll probably just switch my donations from Mozilla Foundation to the Servo project as Mozilla is apparently no longer interested in developing the best possible browser.

          1. 3

            Does anyone know if there are any live projects that build a browser interface around Servo?

            1. 4

              Rewriting Firefox in Servo reminds me of this article from 20 years ago. I don’t think Servo’s approach here was necessarily bad, and Firefox got several new features of functionality from it (CSS engine and maybe others?). Rewriting something as large as a browser requires tremendous resources, though, and it’s unfortunate that it’s not always economically feasible. It makes me wonder if browsers are just good enough at this point.

              Regardless, I’m excited to see Servo have a new home, and not just be abandoned!

              1. 4

                They’re probably too “good” at this point. Can’t have any competition when the complexity of implementing a reasonably full-featured web browser is as high as it is now.

                1. 2

                  If not some sort of big rewrite, what is it that’s going to ever make firefox good? Polishing decisions from 20 years ago also takes a ton of effort, and it doesn’t seem like you’re going to out polish chrome.

                  Not financially feasible when you’ve taken in something like 4 billion dollars in the last 10 years?

                  1. 4

                    4 billion dollars in the last 10 years

                    This is what I’ve always wondered. What on Earth did Mozilla do with all the money they’ve been getting from Google? Firefox OS and acquiring Pocket ate some of it, but beyond that I just can’t wrap my head around it.

                    1. 8

                      400 million revenue a year is certainly a chunk, but it’s also not huge for a company of 1000 people, especially if you are in a business where Google, Apple and Microsoft literally consider you a hiring pool. It’s 400000 budget per year, per employee - of which you need to also cover all infrastructure, CI, security, legal, offices across the globe (plus their attached, external, staff), external costs for marketing campaigns and similar.

                      Firefox is a product with a global and sizable userbase, itself in billions at some time.

                      You gave yourself the answer: the money probably went into “bets on the future”, which mostly didn’t work out. Servo and Rust are products of that phase. One can talk about why they failed (or if they even failed) and what mistakes Mozilla made - but I’m not wondering where the money went.

                      1. 2

                        That all sounds absurd to me. I also don’t want to believe that mozilla is just some giant money fire, but it sure seems to be the case.

                        edit: I was on mobile but I’ll elaborate now that I’m at a keyboard:

                        If you don’t have enough money to actually do anything innovative, and you have 1000 employees, try:

                        • cutting 30 million out of the marketing budget
                        • firing like 300-700 people
                        • not having multiple international offices
                        1. 4

                          That’s a little bit close to armchair CEOing. (also, FWIW, they just fired 250 staff and closed an office)

                          All of the things you mention also come with repercussions (e.g. advertising does bring additional revenue in return).

                          And where does the impression come from that Mozilla does nothing innovative? Just as a list here out of the last decade:

                          • Servo
                          • Rust
                          • Firefox OS
                          • Mozilla Hubs
                          • Mozilla WebThings
                          • Webrender (GPU-rendering) in Firefox
                          • WASM
                          • Mozilla Speech (a crowdsourced, open, dataset for speech recognition)
                          • Worked on and influenced all web standards in that time frame to an extend (I could continue the list, but frankly, I’m a bit tired)

                          If, at all, I’d more look at why many of those things didn’t succeed fully, but saying that the company can’t innovate does not cut it. Rather, the question is how many of the innovations didn’t succeed as products on the market.

                          1. 0

                            Servo, Rust, Webrender, and WASM are all great, and as far as I know, dead. The rest don’t seem innovative the service of the only goal I care about, and what I view as the purpose of mozilla, creating a browser that’s better than chrome. Isn’t webrender a part of servo? I believe the wasmtime team was let go too, I don’t know how much that relates to WASM in general, but it seems everything of interest is gone.

                            It’s not like they’re literally doing nothing, but it sure seems like they’ve squandered a very large fortune working on the wrong things (from my view of firefox being the reason mozilla should exist at all).

                            1. 4

                              Servo, Rust, Webrender, and WASM are all great, and as far as I know, dead.

                              Could you define what “dead” means to you? Rust has been on the uptake for quite a while and is still seeing regular investment and new projects from very large and small companies. Webrender has also recently been enabled on more machines in Firefox 83, so I wouldn’t consider it dead either.

                              The rest [isn’t about] creating a browser that’s better than chrome.

                              I think this depends on what you mean by “better than chrome”. For example, Mozilla speech (and the associated deepspeech/TTS) projects could have resulted in the best browser controllable through speech. Maybe you don’t care about this but I think people with disabilities do, and making something better for people with disabilities makes it better for everybody. For example I don’t have any disabilities and I actually tried to use Mozilla’s TTS (which has amazing results and could have gotten even better with a few more years of work) to read web pages.

                              I’m fairly certain that you could present each of Mozilla’s projects as making the web browser better. The real issue isn’t about whether Mozilla is attempting to make Firefox better but about whether your definition of better matches Mozilla’s.

                              1. 2

                                The whole WASM backend team also just got hired by Fastly, and WASM in the browser is still maintained by Mozilla.

                                The whole thing with speech also has a different angle: there’s no free libraries for that with a large corpus, which means Amazon, Apple and Microsoft are literally the ones you need to get by. Mozilla Speech could have been disruptive (and was a little, there’s quite some use out there).

                                Also, about Rust: Mozilla’s Rust team was already only 2 people. The rest were working on technologies that happen to have used Rust. Many of them now found 100% jobs working on Rust elsewhere.