zlacker

>>embedd+(OP)
I haven’t studied the project that this is a comment on, but: The article notices that something that compiles, runs, and renders a trivial HTML page might be a good starting point, and I would certainly agree with that when it’s humans writing the code. But is it the only way? Instead of maintaining “builds and runs” as a constant and varying what it does, can it make sense to have “a decent-sized subset of browser functionality” as a constant and varying the “builds and runs” bit? (Admittedly, that bit does not seem to be converging here, but I’m curious in more general terms.)

>>Pinus+uK
...What use is code if it doesn't build and run? What other way is there to build a browser that doesn't involved 'build and run'?

Writing junk in a text file isn't the hard part.