3 ms·
Fair. I meant JS here as in "fully DOM compatible, as-used-in-your-browser JS". JS engines themselves aren't that hard to make (I think there's about 9 or 10 ac
by noirscape 4y ago
Fair. I meant JS here as in "fully DOM compatible, as-used-in-your-browser JS". JS engines themselves aren't that hard to make (I think there's about 9 or 10 actively maintained ones?), but to make one that's usable in situations that aren't things like node or as a sub-language in a different project... that's far more difficult.
- cxr 4y ago> "fully DOM compatible, as-used-in-your-browser JS" That's still wrong. s/DOM// s/JS/DOM/ Continuing to say JS when you're really talking about what is, again, still in the land of HTML, CSS, etc just confuses things. Viz: > to make [a JS engine] that's usable in situations that aren't things like node or as a sub-language in a different project... that's far more difficult It's really, really not about JS. You don't make a browser that's compatible with the Wild Wild Web by adding stuff to the JS engine. You do it by implementing moar browser.