Return Styles: Pseud0ch, Terminal, Valhalla, NES, Geocities, Blue Moon. Entire thread

Why browsers are bloated

Name: Anonymous 2014-07-27 0:20

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?

Name: Cudder !MhMRSATORI 2014-09-02 9:43

>>124
Wine32 on a Nehalem.

More benchmark results... this time using a ~1MB HTML file (http://www.w3.org/TR/html5/syntax.html )

Tokeniser + Parser: 190-200ms (5.0-5.3MB/s)
Tokeniser + Parser, tags/comments only: 110ms (9MB/s)
Tokeniser + Parser, text only: 4250ms (243KB/s)
Tokeniser only: ~5.6ms (180MB/s)

Making DOM nodes and adding them to the tree is the slooooooooow part. That's the code which is currently in C.

That text-only result is interesting... when the input is 100% text with all the tags stripped out, looks like a strcat/strlen is the problem. That was dumb and stupid string handling.

Tokeniser is more than fast enough at the moment.

>>126
U MAD? Refer to >>120.

Newer Posts