4 ms·

Servo had always been an experimental renderer and most of its successful parts have already been merged in Firefox. It's been years, can you stop beating this

Servo had always been an experimental renderer and most of its successful parts have already been merged in Firefox. It's been years, can you stop beating this merged horse? Embedding Firefox doesn't increase marketshare and protects more people from tracking. Nobody gives a shit that your Electron app runs with Firefox and not Chromium. Now, I do agree that the Mozilla CEO pay is way too high, but holy fuck find something new and useful to complain about.

GeckoEidechse 4y ago
In regards to Mozilla creating an Electron alternative, they already tried that. It was called Proton and it never caught on but was solely bleeding money so they had to shut it down again.
- lucideer 4y ago
  Proton was never mature or stable so saying it "never caught on" is a bit of a joke. It was never released. It also wasn't equivalent to Electron for a bunch of big architectural reasons related to required changes to Gecko that the team never prioritises because Proton wasn't a priority project. > was solely bleeding money Yes. Because unreleased in-progress projects should be profitable before they're released in order to be viable. How much money was it bleeding? Do you have eyes on these accounts?
modo_mario 4y ago
>Servo had always been an experimental renderer and most of its successful parts have already been merged in Firefox. Wasn't it supposed to be a full on replacement? I get that they were still a long way off but it seemed like they got really far and what was there was super promising.
- ohgodplsno 4y ago
  Nope. Servo was always a research project, meant to explore what was possible. Making a new browser engine from scratch is a stupidly long undertaking, and unless you're the SerenityOS guy that can afford to not have half the sites not working because you'll be working on it for the rest of your life, the only people that believed it would be a full on replacement and pushed that theory were reddit zealots. Servo gave the following to Firefox: * Proof that Rust can both be used to make browser engine components and easily integrate, with really good performance. Servo served as a way also to test out Rust changes and pain points that needed to be addressed. * Stylo, a CSS rules engine. * Neqo, an HTTP/3 library * WebRender, the multithreaded rendering architecture that everyone was really thinking of when mentioning Servo Which is really pretty much all of Servo. Html5ever is fun but unneeded.
  - modo_mario 4y ago
    >Servo was always a research project, meant to explore what was possible. I suppose you're probably right but then why do they say "Servo’s mission is to provide an independent, modular, embeddable web engine" >Making a new browser engine from scratch is a stupidly long undertaking I remember running their testing snapshot thing a long time ago. It seemed like they managed?
deleted 4y ago
[deleted]

GeckoEidechse 4y ago

In regards to Mozilla creating an Electron alternative, they already tried that. It was called Proton and it never caught on but was solely bleeding money so they had to shut it down again.

lucideer 4y ago
Proton was never mature or stable so saying it "never caught on" is a bit of a joke. It was never released. It also wasn't equivalent to Electron for a bunch of big architectural reasons related to required changes to Gecko that the team never prioritises because Proton wasn't a priority project. > was solely bleeding money Yes. Because unreleased in-progress projects should be profitable before they're released in order to be viable. How much money was it bleeding? Do you have eyes on these accounts?

modo_mario 4y ago

>Servo had always been an experimental renderer and most of its successful parts have already been merged in Firefox. Wasn't it supposed to be a full on replacement? I get that they were still a long way off but it seemed like they got really far and what was there was super promising.

ohgodplsno 4y ago
Nope. Servo was always a research project, meant to explore what was possible. Making a new browser engine from scratch is a stupidly long undertaking, and unless you're the SerenityOS guy that can afford to not have half the sites not working because you'll be working on it for the rest of your life, the only people that believed it would be a full on replacement and pushed that theory were reddit zealots. Servo gave the following to Firefox: * Proof that Rust can both be used to make browser engine components and easily integrate, with really good performance. Servo served as a way also to test out Rust changes and pain points that needed to be addressed. * Stylo, a CSS rules engine. * Neqo, an HTTP/3 library * WebRender, the multithreaded rendering architecture that everyone was really thinking of when mentioning Servo Which is really pretty much all of Servo. Html5ever is fun but unneeded.
- modo_mario 4y ago
  >Servo was always a research project, meant to explore what was possible. I suppose you're probably right but then why do they say "Servo’s mission is to provide an independent, modular, embeddable web engine" >Making a new browser engine from scratch is a stupidly long undertaking I remember running their testing snapshot thing a long time ago. It seemed like they managed?

deleted 4y ago

[deleted]