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?

>>744,746

static link

That's even worse.

>>745
Yes, a shitty inefficient version can be done in almost no time. I could probably have an acid2-passing horribly bloated browser-ish thing if I just used C++ and banged out classes all day long for a week. That's not the point. It's taking so long because [1] I have tons of other stuff to do and [2] I'm thinking carefully, very carefully, about how to do it. Amortised over the past few months I've probably been spending less than an hour a day on this.

>>747 start reading around >>123. Parser is overall twice as fast as Chrome's, less than 1/10th the size, and that's with a stupid C part I haven't done much optimisation on yet.