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?

>>958
Are there any sites (besides contrived limit-testing test cases) that come anywhere near those limits? How about showing some examples instead of spewing vague "generating CSS and queries automatically " bullshit? That's the sort of attitude that leads to insane ENTERPRISE solutions where 99% of the complexity is there just for 0.1% of the use cases.

WebKit has a maximum nesting depth of 512:

http://trac.webkit.org/browser/trunk/Source/WebCore/page/Settings.h#L206

Firefox is lower, at 200 (not even a byte):

https://hg.mozilla.org/mozilla-central/file/050887c64183/parser/htmlparser/src/nsHTMLTokenizer.cpp#l382

There's no point in having more than 255 attributes per selector either, since HTML5 doesn't define that many. Look at the discussion about CSS property maps above - why use a data structure optimised for thousands or more elements and is dynamic-everything, even if it's "theoretically more efficient", if you will never put more than a dozen or maybe 100 at most in it? Premature generalisation. That's real bloat.