Return Styles: Pseud0ch, Terminal, Valhalla, NES, Geocities, Blue Moon. Entire thread

Why browsers are bloated

Name: Anonymous 2014-07-27 0:20

https://github.com/WebKit/webkit/blob/master/Source/WebCore/platform/Scrollbar.cpp
https://github.com/WebKit/webkit/blob/master/Source/WebCore/platform/win/ScrollbarThemeWin.cpp
Let's reinvent the fucking scrollbar, which every goddamn platform with a UI already has, and make it behave subtly different from the native one!

Right-click a native scrollbar in some other app:
- Scroll Here
- Top
- Bottom
- Page Up
- Page Down
- Scroll Up
- Scroll Down

Right-click a scrollbar in Chrome:
- Back
- Forward
- Reload
- Save As...
...

Right-click a scrollbar in Firefox and Opera:
Absolutely fucking nothing happens!

What the fuck!? How did these terminally retarded idiots get involved in creating one of the most important pieces of software to the average user?

Name: Anonymous 2016-03-13 3:22

>>852
Stop thinking tiny, like a tiny brained fuck.

Consider a system with a caching filesystem, compared to one without. The caching one is larger, both in code and memory footprint, but is going to be hella faster than any simple disk access code that hits the drive every time.

Consider a JIT compiler, versus a bytecode interpreter. Which one is "bigger" and "bloated", and which do you think run faster?

Consider any system with actual brains in it, be it predictive analysis and heuristics, or just something which has been hardcoded & optimized for AOT measured slow paths.

And that's not even getting into tons and tons of benefits of larger architectures for being able to configure, debug, and instrument what the fuck is going on in your computer, instead of your shitty opaque asm code.

You are clueless and bring no value to the world, defending your absolute shit to the very end. I hate hearing your ignorant, anti-reality blather. Not just this, but every single word you've said. Kill yourself.

Newer Posts