Again, Stephan has created and maintained multiple (46 in fact, [1]) treatments on what he has learned about v8. He even separated and a special wiki category, called "BitchAndMoan" [2], just so people wouldn't be confused about what were personal critiques and what were technical critiques. This isn't an "HN echo chamber" or a "woe is me circle jerk". This is a critique of Google's technical handling, feeding and nurturing of a (non-)product. I've embedded JavaScript for almost 15 years, since Mozilla's SpiderMonkey was ported to DOS/DJGPP[3][4]. There's dozens and dozens of successful embedders of various size and purpose [5][6] supported by Mozilla via SpiderMonkey and/or Rhino. While in college, I added LAM/MPI hooks and developed multi-monitor applications years before multi-monitor graphics cards were commercially available. Stephan is a former SpiderMonkey embedder[7]. I'm former colleagues with Shanti Rao of JSDB (SpiderMonkey) while at NASA/JPL [8]. There is a huge difference in support in what Mozilla provides [9] vs. what Google provides [10]. Stephan's critique is, without a doubt, a fair critique.

[1]http://code.google.com/p/v8-juice/w/list [2]http://code.google.com/p/v8-juice/wiki/CommentaryOnV8 [3]http://marc.info/?l=freedos-dev&m=94670703232745 [4]http://web.archive.org/web/*/http://dominic.liquid3.com.au/j... [5]https://developer.mozilla.org/en-US/docs/Web/JavaScript [6]http://en.wikipedia.org/wiki/JavaScript#Uses_outside_web_pag... [7]http://spiderape.sourceforge.net/ [8]http://www.jsdb.org/ [9]https://developer.mozilla.org/en-US/docs/SpiderMonkey [10]http://code.google.com/p/v8/w/list