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?

CSS parsing. The way the spec is written makes it seem like you have to extract the whole series of tokens for the selector before parsing them separately, when all that's needed is to parse the selectors at the same time as everything else, as they come from the tokeniser. I wonder how many implementations out there needlessly allocate a secondary array of tokens (or allocate tokens, for that matter) just so it can rescan them to parse selectors...

It's also funny to see developers chasing the parallelism dream with things like Servo that have only demonstrated at best 2-3x speedup with multiple cores and even more complex code, when I can probably get 10x speedup with simple, single-threaded Asm that's at least an order of magnitude smaller. The CSS matching is also easily parallelisable if I really want to.