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?

>>892
http://c2.com/cgi/wiki?DesignForPerformance

I already got bitten by a stupid design decision in >>133. Also consider that other browsers already have a lot of (complex) optimisations because of how old they are, so if I want to compete I can't not optimise. These optimisations I'm doing actually simplify the code, so there's another benefit -- I take less time writing it and reading it in the future.

>>894,896
You don't need 64 bits if most of them are going to be zero. 64-bit pointers with around half their bits 0 make me want to facepalm every time I see them. Besides, amd64 is a fucking mess of RISC-ism and 8 registers is enough for a lot of things if you use them well. Compilers are just retardedly stupid at register allocation. (Just look at the dismal performance of MIPS with 32 registers... More is not better, except in synthetic microbenchmarks.)

What do I need firefox hello and firefox pocket for?

You don't, Mozilla does. You are the product.