it’s a testament to how hard the Firefox team works that their browser remains competitive against an aggressive monopolization project by one of the biggest corporations in the world, all while Mozilla as a company does their best to fuck everything up
I think the community has tried to pick up the project again recently, but it’s obviously slow going without sponsorship and full time devs: https://servo.org/
I just ran the nightly build and it looks like their css support is still quite far behind. I hope they can make progress though. It’s such a mammoth task
I was thinking along those lines too. I’d love to use servo for projects where I know exactly what I’m going to render, or even as a docs viewer where imperfect rendering is ok
it’s a testament to how hard the Firefox team works that their browser remains competitive against an aggressive monopolization project by one of the biggest corporations in the world, all while Mozilla as a company does their best to fuck everything up
it’s a shame the project to rewrite the engine in rust, I think?, was cancelled.
I think the community has tried to pick up the project again recently, but it’s obviously slow going without sponsorship and full time devs: https://servo.org/
Oh wow, thanks for sharing. Their task list must be huuuuuuge
I just ran the nightly build and it looks like their css support is still quite far behind. I hope they can make progress though. It’s such a mammoth task
Yeah, supporting every css feature in the world is a tall order. I would love if:
Servo supported a small but useful subset of css features (e.g. just grid and flexbox for layout)
Servo was embeddable like a WebView or electron.
Then you could use the supported subset and not have to worry about supporting every crazy feature, and hopefully get a faster lighter WebView for it.
But even that’s a lot of work.
I was thinking along those lines too. I’d love to use servo for projects where I know exactly what I’m going to render, or even as a docs viewer where imperfect rendering is ok