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?

>>56
I bloody well hope not! How much energy (human and machine) needsd to be wasted on figuring out [i]where to split a line of text[/i}!?!?

In fact I am used to systems that do not even tr
y to split at whitespace. If the available width
is x columns wide, they would just split the li
ne at that position, no exceptions. Easy and com
pact and really not so hard to read if you're us
ed to it, but I don't think the majority will li
ke this, so for my browser I will compromise on
an algorithm that doesn't split words, but is no
t any more complicated than that.

When people read webpages, their primary goal is to consume the content, the information (no matter how vapid it may be.) The majority of them are not there to gawk at the linebreaking or font rendering, so any added complexity there for small improvements will be imperceptible and wasted for almost everyone. Don't even get me started on the idiocy of "smart" quotes, ligatures, and all that other extraneous shit.