/updated > If I had to name the parts of Servo I'd love to drop, it wouldn't be what you think ... Interesting. > I think you're under the impression that ne

/updated > If I had to name the parts of Servo I'd love to drop, it wouldn't be what you think ... Interesting. > I think you're under the impression that new Web sites tend to avoid all the "goop". Well as a web developer myself I do realize I'm adding a lot of workarounds, that's part of my frustration. It seems counterproductive for you guys as engine developers, and us web developers to use such an ever increasing amount of code just to work around stuff we throw at each other. > Presumably for OpenSSH, if you control the server and it's properly configured you can drop the ugly, old code. Not so on the Web. Old and new Web sites alike rely on all sorts of corner cases. Maybe for OpenSSH, but I think OpenSSL suffers from the same legacy compatibility issues as a browser. Still LibreSSL took an OpenSSH like approach by separating out all system specific exceptions from the base and put them in a different portability package. > ... (ELinks, for example). You aren't using them because they don't support enough of the "ugly" features. I'm not using elinks or other text based browsers not because they miss a lot of features, but because they're not as secure as I did expect from a text based browser[0]. They are still full of all sorts of features[1] that add to it's complexity without having enough value, imho. I think it's a feature to be not full featured. [0] http://marc.info/?l=openbsd-tech&m=140516601718662&w=2 http://marc.info/?l=openbsd-tech&m=140516601718662&w=2 about gopher support in lynx [1] Elinks: Full-Featured Text WWW Browser - Lots of protocols (local files, finger, http, https, ftp, smb, ipv4, ipv6) http://elinks.or.cz/about.html http://elinks.or.cz/about.html