That, combined with event based non-blocking apis for managing multiple tasks neatly covers more or less everything you can do in many other mainstream languages like Python and Ruby (excluding some magic in native code extensions).
Given the way that JS performance has been moving, that would indeed be able to take on quite a workload, if you can run a decent number of "webworkers" at a time.
I presume its anticipated niche is as a CGI-type replacement --- relatively light-weight 'programs' executed per request. If that's the case, is there much need for multithreading?
In 2009, my default presumption is that an emerging platform that probably won't even be viable until 2010 ought to have a concurrency story better than what we already had. If it doesn't have that, why wouldn't I use an existing language?
If it were entering a vacuum, sure, great, no problem, but it's not.
I guess this goes back to my old standard for examining the usefulness of a language: "What problem does it solve?" There ought to be a single sentence that says what problem the language solves. Python: "It's too hard to program; we need to make it easier." Perl: "Too many separate UNIX tools, we should merge them together." Haskell: "Our academic theory is great and all, but we need to come out of our ivory towers and prove it works.
Javascript on the server: "..."? "I really want to be able to use the same language on the server as the client" is a I think what it's going for, and as far as that goes it's ok, but my objection is that it isn't a very good server language. And note my objections really are about the language, not merely a lack of libraries, which is completely solvable. You can't just graft on concurrency anymore, at least not as far as I'm concerned; my standards have risen.
I'm curious as to why you think JavaScript can't hold it's own weight against said-languages for the server-side?
there was a rather long concurrency discussion on commonjs http://groups.google.com/group/commonjs/browse_thread/thread...
there was no consensus and the topic was delayed for later discussion - but it seemed the promises idea got most attention (my pov) http://wiki.commonjs.org/wiki/Promises
Concurrency is important, but I think most server tasks don't require it. JavaScript doesn't need to be the 100% language to "win" it just needs to be the 80% language.
Wouldn't be hard to implement the rendering part as WebWorkers.
(I say I will "run screaming" not merely because I don't want to deal with it, but because I don't want to deal with yet more libraries based on shared-state concurrency. No. I've left that behind and I'm not going back, and certainly not in a space where I've got an abundance of languages to choose from.)
Without a solution to that problem, I see this as a terribly, terribly wrong move, and a terrible time for JS to try to be picking up the server. Servers are in the multicore age and have been for a couple years now.
(And if your answer is "well, we'll just keep all the tasks simple and we won't need multiple threads", I would remind you that you're running on the server, which often needs to do, you know, actual work. A language that can't do that may have a small niche, but it's going to be an uphill battle against entrenched competitors.)