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?

>>63
At this point it would probably be better to share ideas only.

>>64

really, how open is a protocol if you need a team of hundred programmers to implement it?

Maybe you don't. That's what I'm trying to do - find simplicity in complexity.

a protocol that cannot be implemented by a programmer in his spare time over a week is not open

Depends on what it does. There's justifiable complexity, and there's extraneous complexity. The former is fine, the latter is the problem.

>>67
:facepalm:

>>71

they're powerful because byte streams are easily mungeable

They expose the full power of letting the application interpret data as it wants to. The complexity and annoying failure modes of trying to enforce a type on the data make it a stupid thing to do - remember resource forks on old MacOS and the typed (text, binary, record, etc.) files used in old mainframe systems? Not surprisingly, they disappeared.