Am I the only one completely unfazed by this? This seemed like a cool thing, I looked into it a little bit more wondering "How are graphic API calls translated

Am I the only one completely unfazed by this? This seemed like a cool thing, I looked into it a little bit more wondering "How are graphic API calls translated? What about filesystem calls in browser? How do I manipulate the DOM?" and delighted of a new world that would open to me. And I ended up on my answer: https://gist.github.com/jgranick/5430948 https://gist.github.com/jgranick/5430948 Sure, that is pretty tame CPP code, nothing too hard. And then I looked at the JS demonstration and Chrome decided to give 120MB of RAM to displaying a triangle. Okay, Chrome may be slow sometimes, things happen,... curl --silent http://www.joshuagranick.com/examples/simplegl/SimpleGL.js | wc -l 125018 Oh shit. Well, right. The whole "CPP2JS" boilerplate is there. I won't even entertain the thought of reading past the first screen of 125K lines of computer-generated source code so I'm gonna ask: what is the point to this? There is no native "manipulate the DOM" function in CPP that could be translated to the original JS one and it takes me 125 thousand lines to draw a triangle: what can we gain from this? Don't tell me "speed", my computer lost it on I/O alone.