4 ms·

Hi Joshua, My name is Peter Sherman. I wrote a non-HTML, non-CSS, non-JavaScript browser several years ago (in theory, it could be easily adapted to those sta

Hi Joshua, My name is Peter Sherman. I wrote a non-HTML, non-CSS, non-JavaScript browser several years ago (in theory, it could be easily adapted to those standards by including code and hooks for the appropriate parsers and interpreters. (Software Engineering side-observation: Why aren't browsers delivered as independently functional component parts, that is, why are the codebases for most browsers that use a lot of libraries typically tightly coupled to those codebases?)) Anyway, point is, I may be able to help you with your quest if you reach out to me... my email address is: peter.d.sherman@gmail.com I can give you all of the basic theories with respect to what you're trying to do, and hopefully make the software engineering process a little bit easier by showing you how to appropriately divide ("divide and conquer") the entire task into much more managable, approachable, and understandable subcomponents... Let me know, and I'll try to help you! Anyone else who is similarly curious can also reach out to me, via email, too! If more than one person is interested -- perhaps we should put together a group?

zzo38computer 3y ago
> Why aren't browsers delivered as independently functional component parts Actually, independently component parts is what I think should be done, would be better, that you can exchange each part, add new parts, or wire them together differently, e.g. you can much more easily change some features in ways which are not as easily done, e.g. replace the TLS implementation with your own that allows non-TLS proxies, or to change some CSS commands, or add new HTML commands, without changing everything else too.