> The one question I have with such a suggestion is how much code do you > expect to share with the node ecosystem?
I suppose if the answer is zero, this is what I've also been looking for! A syncronous javascript engine for little syncronous scripting tasks. Not web-serving, not web-scale etc. Just some routine tasks to calculate. It just doesn't exist yet. But honestly this is nothing node.js should care about. Pulling together the V8 into a syncronous script executer isn't hard, the V8 comes even with a prebuild demo console. The hard part is establishing an alive ecosystem around that, and I don't see that coming. As we know from other language, language is one part, a sized standards library and solutions ecosystem is another, and the second is difficult to pull off. Node.JS has an alive ecosystem, and so far its simpler to workaround the async style for that one, rather than trying to set up an alternative ecosystem. PS: I'll just pretend it isn't an April fools... -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
