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?

>>429
Give me some time to clean it up first...

>>458
Yes, native Win32.

>>466
https://code.google.com/p/plan9front/source/browse/sys/src/libhtml/lex.c#594
- Nearly 1.5K lines of C (my tokeniser is <1K lines of x86 Asm)
- Allocates (and presumably frees somewhere else...) every single token - how in $deity's name can anyone think this is necessary?
- Tons of reallocs (not even exponentially growing the buffer, only linear, so quadratic time overall!) I showed how bad this could be in >>131,133
- Doesn't look compliant with HTML5

Then I look at
https://code.google.com/p/plan9front/source/browse/sys/src/libhtml/build.c
and the first thing I see is a fixed-size array for an element stack, one thing that certainly deserves to be dynamically allocated/resizeable?

This one may be "simpler" than something like Gecko or WebKit, but seeing these elementary mistakes in presumably more "efficient" and "less bloated" software (these Plan9 guys should know more than me...?) is still a big... FAIL!