Why browsers are bloated

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?

>>791
WHO THE FUCK CARES? The very nature of the HTML/CSS/ES specs demand a fuckton of state, especially if you're going to have decent dynamic response times, and you're quibbling over the number of bytes in a function call.

You have no goddamn idea what makes bloat and what doesn't. There's assburgery nitpicking, which can be somewhat amusing, but this is just being a fucking retard.

>>791
Surely if you're hand-optimising the rest of your program in ASM your bottleneck becomes the dynamic libraries that (a) are more often than not going to be written in C and "optimised" by some crappy compiler, and (b) going to have wildly variable performance characteristics on different systems, as they will use different compilers, different library implementations and different versions of libc.

The size of the functions alone (which is apparently your primary concern with static linking) should surely be a negligible cost when taking everything else into account.