I can’t get a straight forward answer on this. Is Google’s V8 engine really limited to 1 VM per process?
If google’s v8 engine is limited to only 1 VM per process, then doesn’t it sort of exclude itself from being used in libraries? Say I code up a c++ library that uses V8 called LibA. And someone else codes up another library that uses V8 called LibB. If an application links to both LibA and LibB bad stuff would happen (right?).
I need a fast (with speed being the most important requirement actually) javascript parser for a lib I’m trying to write, but I don’t want to use v8 if I’ll run into this problem (it’s likely that the kind of applications that link to it will also use v8 at some point).
Based on this closed bug report, it’s safe to say that Google’s V8 engine is not limited to a single thread per process (since approximately April 2011).