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?

>>39

I don't see how using excessively verbose code with tons of needless indirection/abstraction and mind-numbingly-long variable names is in any way more productive. The same goes for reimplementing basic UI functionality and creating trivial classes - it's busy work, useless time-sinks to give the impression of being productive.

I don't think you completely got my point. I'm saying the world of paid programming values productivity a lot more than they value optimal design. Programmers who produce verbose code that achieves the specifications within a shorter timeframe are valued higher than programmers who take longer to produce optimal code and design. I'm not judging the value of this being good or bad, I'm just saying that this happens.

The same goes for reimplementing basic UI functionality and creating trivial classes

I am not the designer of Chrome and I cannot give any rationale why they chose to work this way. I can only assume they had a good reason to specify this as a feature.