posted by dennisn on November 9th, 2011 at 10:06PM
So what? This doesn't address any of the very serious problems I have with JavaShit -- which are mainly client-side -- namely that it (my implementation) consumes absurd amounts of CPU to render bloody text/images, that it ruins the parseability/semantics of webpages, that it introduces all kinds of security holes, not only directly via unaccountable centralization of the code, but indirectly via unecessarily open doors and bugs.
In terms of this off-topic server-side stuff, I've been using lighttpd for a long time now -- you sure it doesn't do the same stuff, perhaps even better? I don't see anything unique with "Node" that can't be accomplished by any of the other competitors, via a module or patch or something. (It's not that hard to queue i/o, or to lower thread footprints). And, it seems to me like this has nothing to do with JavaShit, but rather with this "V8" thing -- ie. it's V8 that seems to have the more efficient resource usage? But probably not any of the other JavaShit implementations? So you probably meant "moar v8".
|