Re:Servo in 2024: stats, features and donations
by codingbot3000 on Thursday February 06, 2025 @05:04AM
(#42960859)
That's really a good point. If you're building a native app or similar, why constrain yourself to HTML?
Re:Servo in 2024: stats, features and donations
by iudqnolq on Thursday February 06, 2025 @05:38AM
(#42961028)
Because flexbox & grid are amazing. And you'll probably need it anyway if you ever have to render arbitrary rich text.
Re:Servo in 2024: stats, features and donations
by filleduchaos on Thursday February 06, 2025 @07:58AM
(#42961897)
Flexbox, grid and rich text are not the sole domain of HTML.
How do people imagine rendering is implemented in browsers to begin with?
It just happens to be the most widespread by accident, because hyperlinked documents - HTML - became huge and then more and more UI elements were bolted on top of it. And suddenly it became the goto, because the plattform run everywhere.
But it is still a ugly mess underneath and you might be right, that it is the future, but it is not a great one. I hope a great one will surface one day and then we can start new with something sane.
"I'm excited for the new crop of browser engines because they could fix those deficiencies"
And I cannot see what fixing those deficiencies could mean other, than throwing most of the standard away. It doesn't mean all of it needs to be thrown away. WebAudio API, WebGPU, etc. all became great standards. But simple UI elements, like a slider or color picker are still just ugly and impossible to make beautiful and behave sane, besides making a new one by hand, or using a libary from someone who did that. But - with WebGPU especially - I am excited for the possibility to build a sane framework on top of some subsets of the browsers capabilities.