News for hackers. Stuff that matters.
Re:Lazy deserialization by edf13 on Monday February 12, 2018 @01:56PM (#16360945)
Good work - but can we just take a minute to look at this...

> Over the past two years, the snapshot has nearly tripled in size, going from roughly 600 KB in early 2016 to over 1500 KB today.

1.5MB per snapshot... per tab effectively! It's crazy how wasteful we've become.

Re:Lazy deserialization by jaawn on Monday February 12, 2018 @02:51PM (#16361454)
I have thought for awhile, and continue to think, that developers avoid "premature" optimization too fiercely. Yes, there are diminishing returns with optimization effort, but too often people interpret "avoid premature optimization" as "never optimize unless it feels slow, and even then only if it feels slow when it's the only thing running. Otherwise, blame everything else that is running first!"
Re:Lazy deserialization by drak0n1c on Monday February 12, 2018 @03:27PM (#16361757)
Not to mention that the "never optimize until it feels slow" judgement calls are usually conducted on Macbook Pros with fast internet.
Re:Lazy deserialization by jaawn on Monday February 12, 2018 @05:00PM (#16362725)
Oh absolutely. I have been noticing this is starting to happen with SSDs as well. A lot of modern games run awful on mechanical drives.
Re:Lazy deserialization by cobalt on Monday February 12, 2018 @07:14PM (#16363643)
that's unfortunately because we are pushing fancier and fancier models with higher and higher resolution textures
Re:Lazy deserialization by taeric on Monday February 12, 2018 @02:57PM (#16361497)
Indeed, the quote of Knuth on this is followed immediately by not neglecting that critical minority of code where it matters.

Sadly, the promise of zero cost abstraction is a huge siren call. And not likely to change anytime soon.

Re:Lazy deserialization by jaawn on Monday February 12, 2018 @05:33PM (#16362994)
"Zero cost abstraction" is like a sarcastic joke at this point in web development. If you pull up performance comparisons for web backends, a lot of the popular ones based on interpreted languages are absolutely abysmal when compared to c++ or Java code (Node is a good example). Many definitely have streamlined development workflows and have nice, high-level abstractions, but at a cost to performance. I don't mean that Node is useless or something, sometimes it makes sense, but it still forces you to compromise.

Front-end frameworks are even worse. A lot of older (but not "ancient") PCs are unusable on the modern web because of poorly-optimized JS or Adobe Flash (a decent portion of this issue is also due to the inherent inefficiency of JS and Flash as well). Fortunately, Google has been making strides with V8, Mozilla did awesome with Firefox "Quantum" and everyone is slowly ditching Flash, but performance still seems to be an ever-present issue.

Re:Lazy deserialization by taeric on Monday February 12, 2018 @08:16PM (#16363972)
Fully agreed. I might extend it beyond web.

It does seem to be getting comical.

Re:Lazy deserialization by CurtHagenlocher on Monday February 12, 2018 @02:13PM (#16361116)
I vaguely remember Lars Bek saying ~8 years ago that the snapshot size was 50kb (at the time).