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

Several people in this thread state "It's cached, so why does it matter?"

So, even ignoring the issue with cold caches, how about the two megabytes of code that the browser may need to go through to render the page?

What on earth is twitter doing on a given page that needs two megabytes of code?*

* As of March 2012, for I'm sure this will look silly when there are 2 gigabyte pages, 20 years from now.



I looks like most of the inline JavaScript is there to handle DOM abstraction and events. Every click essentially needs to be able to build a part of the page client-side.


I don't think we'll have 2 gigabyte codebases..


Higher resolution displays, bump/texture maps for live 3D rendering, 8K video, etc could all contribute to huge page sizes.




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

Search: