3 ms·
>And now a major browser's UI is built with web components! Proud that you need to use your HTML/JS engine to render your UI instead of using faster native cod
by ahbyb 7y ago
>And now a major browser's UI is built with web components!
Proud that you need to use your HTML/JS engine to render your UI instead of using faster native code? I mean you have the opportunity of getting rid of XUL and instead you change it... for something similar?
- adrian17 7y agoAs for XBL: as far as I understand, it was closer to Custom Elements - defined at XML/JS layer instead of with native code. In fact it was so similar that FF developers made a tool that tried to automatically convert an XBL binding to equivalent Custom Element (similar to Python's 2to3).
- spankalee 7y agoThey get the benefits of cross platform code, but now use something that developers are more familiar with, and the can get rid of a lot of code. Big win, I think.
- dralley 7y agoThe browser UI was already rendered by Gecko, that's how XUL and XBL work. It's just that it's rendered by parts of Gecko that aren't used by anything else on the web, and so in honesty those paths probably had less optimization, not more.
- stefan_ 7y agoThat sounds like a great thing, because the Web is where we applaud people if their site renders in a second, enough time for a modern processor to render a full fricking playthrough of the original Doom.