, , to ignore Chrome's anti-ad-blocker changes, despite shared codebase


Perhaps the shared codebase is the problem here? Insisting on anything else, because companies don't want to put in the work to have an independent engine is just dancing around the issue. They're still supporting browser monoculture, ultimately has the engineering resources to make it difficult to sync with upstream, they also control extensions/the store.


Ultimately, there's not even a need to start from scratch on a new engine, is pretty far along and having even minimal resources invested into it from outside / would surely help it towards a 1.0 much sooner.

If these companies are willing to work with Google, why not Mozilla?

I realize, it would be more work to get Servo production ready in the short term, but would maintaining a fork of Blink be so much easier as similar user-hostile changes pile up upstream?

@MatejLach personally I can't wait until servo can be easily integrated in minimalist keyboard focused type browsers... A luakit, vimb or qutebrowser on top of servo would be awesome.

@MatejLach but Servo is just an experimental engine in which stable portions get ported to gecko

@succfemboi That's the path they decided to take in order for to start seeing the Rust improvements quickly, since finishing Servo & replacing Gecko as a whole would probably take many more years and they basically wanted to see the benefits of their investment in ASAP.

But if more companies invested resources into getting Servo to the finish line, there's no reason why it couldn't be used as a replacement engine. It's only experimental, due to the small manpower it has now.

@MatejLach does mozilla want this though? iirc, servo is their playground where they can try new things (like webAR). And getting production users into the project would make these experiments more difficult :/

Mozilla does however offer an easily-embeddable version of Firefox's engine (Gecko) for Android, called GeckoView:

@zalandocalrissian That's a good point, am not sure if would want that, (however they could always have multiple channels, where experimental features only reach stable once no longer experimental).

One thing I do know; nobody wants to build anything new on , fairly or not. Hence I feel collaborating on Servo would have the best chance vs the Blink monopoly, (and WebKit is too similar to be considered meaningfully different + controlled by another corporate entity, .)


Multiple channels would bind resources though. Iirc, mozilla's long term goal is not to replace gecko with servo, but to integrate servo's good/mature parts into gecko. (quantum CSS already landed/webrender is on the way mozillagfx.wordpress.com/2019/ ) While gecko doesn't have the riir/hipster pull factor of servo, it's on par with chrome's performance, and actually faster than servo for many scenarios, because some parts of servo aren't really optimized.

@zalandocalrissian @MatejLach Mozilla as a whole suffers from inconsistent leadership w/ ill-defined goals. they keep changing the plans of these projects & shuffling developers around, b/c that's what executives do to justify their salaries

that is to say: don't confuse Mozilla's plans with what the developers would rather be doing, or what's ultimately worthwhile

@MatejLach I guess the answer is, Blink is a known beast, whatever problem you have with it, you won't be on your own. Servo is completely new.

Sign in to participate in the conversation
Matej Lach's mastodon

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!