It's impressive that Firefox's DOM layout engine is approximately twice as fast as the Chrome one for large documents. (Vulkan spec loads on 5s in ff instead of 10s with chrome)
=> More informations about this toot | More toots from dotstdy@mastodon.social
@dotstdy I wonder what's going on there (online conversion from some other format to HTML?)? The index.html is half a million lines of HTML, and actually crashes the Chrome tab here after a few seconds...
=> More informations about this toot | More toots from floooh@mastodon.gamedev.place
@floooh it's not generated online, it's just a really big (generated) html file, so the layout itself takes a huge amount of time. :') chrome also struggles in a similar way for really large SVG files.
=> More informations about this toot | More toots from dotstdy@mastodon.social
@floooh but yeah it's hilarious that the view source code can't handle it either. I guess some silly syntax highlighter exploding.
=> More informations about this toot | More toots from dotstdy@mastodon.social
@floooh ah so when doing view source in Firefox it seems to trigger multiple layout steps, which is why it's much slower than actually loading the page which only needs to do a single one. I guess either that kind of thing, or the syntax highlighter causing problems for chrome.
=> More informations about this toot | More toots from dotstdy@mastodon.social This content has been proxied by September (ba2dc).Proxy Information
text/gemini