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 !cXCudderUE 2015-06-06 4:50

You can whine all you want but I haven't seen anyone else in this thread claim to have written any significant parts of a browser either, nor thrown out some ideas... I already have most of an HTML parser done, and moved onto a CSS tokeniser now.

After that it will be CSS matching and the renderer, and then more UI stuff (settings, etc.) Then it may be ready to release.

It's a fun thing to see that when using Asm, you're not forced into the dogma that a program must be composed of functions (or objects). You can jump anywhere, and manipulate the stack to "call" or "return" to the appropriate place. With this the CSS parser becomes so much simpler, much like the HTML one did. The main state machine doesn't even need to check for and handle EOF explicitly - it's getchar() which does, and on EOF it jumps to the right handler based on the return address.

Fuck Dijkstra. He got it all wrong. gotos are the way to go.

Newer Posts