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

Why browsers are bloated [Part 2]

Name: Anonymous 2016-04-23 22:49

Cudder is all talk and no action!

Name: Cudder !cXCudderUE 2017-02-22 12:18

>>228
GUI and maybe the HTTP(S) libs. Asm is tokeniser only, but I want to extend it to the parser too, and entity parsing/copy-to-DOM is also being rewritten in Asm. Looking at compiler output makes me want to facepalm continuously. Fixed calling conventions are stupid. In C I can't pass 6 parameters by reference and have them all in registers; easy with Asm but turns into bloated memory accesses in C.

>>230,231
Yes, that's the point. Netsurf and Dildlo (the former is even larger than a fully-featured browser which does pass Acid2, Opera 9.x) are not "lightweight". They just pretend to be. The former has a ridiculously bloated parser created by GSoC noobs. The latter doesn't have much of a parser at all, yet oddly enough still has this useless crap: https://en.wikipedia.org/wiki/File:Dillo%27s_bug_meter_on_www.nasa.gov.png --- since HTML5 standardised parsing there is really no such thing as a "parse error", and any stream of bytes turns into a DOM. What they call "parse error"s in the spec are just semantic "I don't like this" bullshit. For example <foo a="b"c="d"e='f'g=h> parses sensibly but the prescriptivists shout "no, that's an error, you must have whitespace between attributes" --- even when it's not actually necessary and both human and machine would know exactly how to parse it.

IRL is getting very busy again, not much time for this now.

Newer Posts
Don't change these.
Name: Email:
Entire Thread Thread List