Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Do you have an example of your "pet naive unoptimized UI engine" ? Or some code to show ? :)


It remained in the commercial mobile app I'd used it for, and it's not my intellectual property anymore. There isn't anything ingenious about it anyway.

My point wasn't about how good my pet engine was (because it wasn't), but about the fact how the overcomplicated model of the HTML-CSS-DOM-JS makes it so hard to optimize web page rendering that even an unoptimized prototype UI engine outperforms the browser.

I am amazed by the people who develop browser engines because they do something almost magic of fitting that monstrous dynamically modified DOM into so little memory and making it so fast.

I conjecture that in a naive unoptimized implementation a web browser would consume gigabytes and took a couple of minutes to load an average page.


What a name, good sir! (also, keep it up with this fight, +1-ed)




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: