4 ms·
What use cases are you envisioning where threading will be essential? Or aiming in the opposite direction, what use cases are people envisioning for server-sid
by nkurz 17y ago
What use cases are you envisioning where threading will be essential? Or aiming in the opposite direction, what use cases are people envisioning for server-side Javascript at all?
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?
- jerf 17y ago"What use cases are you envisioning where threading will be essential?" 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.
- swannodette 17y agoWhile I agree with you that the lack of concurrency is problematic in the long run I think that JavaScript on the server will be at least as useful for many web applications as PHP, Python, Ruby, Perl - all of which have modest or non-existant concurrency stories. I'm curious as to why you think JavaScript can't hold it's own weight against said-languages for the server-side?