SebastianVerified account

not to mention RTL support, combining characters, interop with the native accessibility features so screen readers work, ensuring the text doesn't look out of place (using the same font smoothing as native), keyboard accessibility. Text rendering is a nightmare. Good luck :D

i don't want to add to this long list, because i get where ken is coming from and i really do want to see where this exploration goes, but... Cmd-F should be particularly fun to implement

Yeah I don't mean to detract from Ken's awesome work, it's just that there's a LOT of work to get from "cool tech demo" to production-ready. Definitely worth exploring though, even if to only find the edge cases and explore solutions :)

Although, I do wonder if some of the effort to implement non-DOM solutions could instead go towards improving DOM performance to make *everything* faster.

It's definitely deeper in the stack (in the browser itself), but it'd be very impactful. JS engines keep improving in performance, and I'm sure the DOM could have some optimizations done too.

I think Ken is saying he obviously doesn't have the expertise or time to optimize a complicated browser engine. What he's building is a fairly low-friction way (albeit hard) to demonstrate his ideas and those could influence browser vendors.