News for hackers. Stuff that matters.

A comment on Ask HN: Why does 'View Source' issue a new HTTP request?. Parent comment

Re:Ask HN: Why does 'View Source' issue a new HTTP request? by EpicEng on Monday December 19, 2016 @10:40AM (#13212041)
But who does this feature help exactly? A _tiny_ number of users. Chrome is currently using over 3GB on my machine. Anything they can do to trim that without affecting performance is worth it to me.
[ Parent | on HN ]
Re:Ask HN: Why does 'View Source' issue a new HTTP request? by ComputerGuru on Monday December 19, 2016 @10:47AM (#13212086)
3GB is how much memory the _rendered/executed_ source code takes. The source code is nothing. Store it LZ4 compressed in memory and it's less than a rounding error.
[ Parent | on HN ]
Re:Ask HN: Why does 'View Source' issue a new HTTP request? by EpicEng on Monday December 19, 2016 @09:27PM (#13216902)
Yes, I know that, but all of these little inefficiencies add up, and for what? A tiny portion of users who need the developer tools? Not worth it.

This kind of thinking is exactly what leads to our software being as slow or slower than that of two decades ago while running on machines hundreds or thousands of times more powerful.

[ Parent | on HN ]