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?

>>45
Gecko code is actually not as verbose and thus easier to read, despite there being far more of it; I think this is the equivalent of the WK InlineFlowBox above:
https://hg.mozilla.org/mozilla-central/file/a4f779bd7cc2/layout/generic/nsInlineFrame.cpp
https://hg.mozilla.org/mozilla-central/file/a4f779bd7cc2/layout/generic/nsBlockFrame.cpp

Theres's also a lot more comments.

>>47

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.

Code needs to be input, and verbose code takes more time to write - even when using an IDE that autocompletes 40-character-long variable names. Verbose code also comes from overly complex design, which leads to writing more code than is actually needed. The total time spent on design and implementation is likely more than an approach of creating the simplest design that works, and writing the minimal amount of code to accomplish that.