It’s apparently still not ready to be used as a browser engine (and may never be), so what exactly is it for?
[1] https://wpt.fyi/results/?label=experimental&label=master&pro...
Making a new browser engine hurts browser compatibility more than it helps it. It now becomes one more target that needs to be tested against, limitations need to be kept tracked of, etc. The best thing for long term browser compatibility is focusing resources into Blink. In regards to the standard we can use LLMs to cross reference the spec, with tests, and with the implementation to make sure all match.
That’s what makes Google more dominant, and if you think that’s a good idea you should really put down your LLM and go read up on a bit of history. Do you want to live in a world where a single company controls your access to the web? Are you eager to navigate through ad pages with a little bit of web? To have even more of your data mined?
Browser diversity may be a bit annoying for developers, but it is good for users, and developers are users too. When there’s a lack of diversity, everyone but the dominant player is squeezed.
Lol, for Blink perhaps, what about the rest of the ecosystem, the web and the users, like the ones who don't even use Blink?
Very idealistic point-of-view with no basis in reality, sadly, because wouldn't it be nice if we could care about just one engine?
https://github.com/versotile-org/tauri-runtime-verso
Servo doesn't implement the whole web platform, but your own desktop app isn't the whole web. You can generally work around any limitations or missing features. And it might be lighter than CEF or whatever.
And yet, somehow, Ladybird seems to be the darling of the masses (in certain circles at least). Doing vibe-ports to Rust, while going closed-contribution also, in my mind, sits in a marked contrast to the origin story that initially generated so much goodwill.
It... took... long...
But there it was. And it still works.
Just the fact that Firefox got browser tabs before anyone else, and Firebug, just took it to another level compared to all the other browsers available at the time.
From https://fedoraproject.org/wiki/Firefox_Hardware_acceleration
I think that was around 2022-23.
I remember this affecting my laptop video watching a lot. Google meet feeling sluggish on Firefox is also something I remember until very recently..
They want to degrade the experience just enough to get you fed up with FF and go (back) to Chrome, without making it absolutely obvious that's what they're doing.
They often label these things as "regressions" because they don't test on Firefox and take forever to fix them. But I can't help but believe it's intentional.
Firefox was great because it was open source but it wasn’t ever really the “best” browser - it was the best open source browser.
Yes that was implied because IE was not mentioned either!
Rust was started in 2006 (20 years ago) and is now one of the most powerful programming languages, while the Servo project was started in 2012. If they reach parity and beyond of current browsers this could clearly become one of the most important browser engines in the future. Effort very well spent in my opinion.
The setup right now seems to give enough people enough time to work on it to move forward, why on earth would you want to involve companies infamous for their shit software quality, like Samsung?
So sure, Samsung would bundle it with their usual crap, but if it helps making the engine more mature, great, but I also don't see why they would in the first place.
The same would occur again.
That folks want to take it further is admirable. But doubtful Mozilla could have afforded to with their existing commitments.
Because look at Mozilla... You need to get the browser in front of people. A browser that works on the real web, is such a huge project, you cannot do it as a hobby community-funded project for ever. You need user-share-%.
Samsung can put it in front of Samsung appliance users.
You understand that Mozilla Firefox is not funded by the "community" and is completely funded by Google's money. Even donating does not fund the browser.
Mozilla knows that the open source "community" has no money, and cannot replace the amount of money Google is paying them and the employees who work on the browser.
The question is are you ready to fill the $600M a year black hole for Google to NOT pay Mozilla to fund Firefox?
It only makes sense for Servo to get funding from for-profit companies at this point, which is one of the only ways open source can work.
Just that - even if you distribute work to a number of cores (that itself limited), you still need to sync the execution. So unless you have some bigger chunks of computation, the performance increase will be very small.
And yes, there are bigger chunks of work when rendering a web page, but that is typically already outside the css engine and can be distributed without having to rewrite the core engine.
But my comments are a bit generic here, so I am open to comments regarding this particular project.
All this effort to use rust and yet they would not rewrite the JS engine which is the biggest attack surface for memory vulns.