I guess Bruno's basic point is: V8 is client-side. That's where Google's thrust is; that's what they're concentrating on. But SSJS has some unique issues, which

I guess Bruno's basic point is: V8 is client-side. That's where Google's thrust is; that's what they're concentrating on. But SSJS has some unique issues, which aren't necessarily issues on the client side. So it's a natural question to ask if Yahoo, as a company, are thinking of investing millions of dollars (in terms of manpower) on node.js . Jason's response seemed more like "we'll cross that bridge when we come to it". Which is perfectly reasonable (and the norm) in startup-world; but large, established companies with their BCPs and contingency-planning and long product lifecycles don't usually think that way. IMHO, if Yahoo is planning on going all-out for SSJS, they should develop some in-house expertise on V8 so that they can fork it for internal use and not have to wait on Google.