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?

>>327
1. Can be fixed with just the evaluations optimized: Flags
2. Only if really needed on the type of OS, like RTOS and embedded devices. What this really needs is the list of dependencies.
3. Can be removed. Usually not recommended for validations. On a Mass distribution, required (MDr). Personal binaries (PB), no .
4. Same as 2.. Can be removed. MDr, PB up to you.
5. Can be removed. Better system uses version with hash of "update." E.g.: version control systems, delta journal filesystem, GPG signatures, etc..
6. Required, if not binary fails. But with it you can replace many of the above issues.
7. Read 6.
8. Read 2.

Most of these are a personal user case scenarios versus mass distribution, where you HAVE TO notate these things. You can, if you want, tailor your own modified distribution of some base, like the multiple debian clones, and tailor it with the above solutions, for personal use.

At the end of the day, Jailing your applications with access controls is all you really need to do. X binary does not need to know or touch Y.common.dependencies, which they both share. X only knows the locations of a "common" directory where it can find X.dependencies. But Y Binary on it's own jail cannot, under any circumstance, know X binary called common.shared.dependencies. Only the shared.common.directory daemon knows X and Y asked for it, and it tells the AC deamon such, logs it and hashes it.

IoW: Stop using defaults, you silly goose. But thank you for insight. Never thought of this, until now.