Sun Nov 01 2009 11:28:50 PM EST from IGnatius T Foobar @ Uncensored
Subject: Re: Spider Monkey
Even so, I'm still inclined to avoid using it for anything other than
the parser. Mozilla's future is unclear and I think it would be a
strategically bad move to tie our fortune to
Anyway, the only reason I was erring on the side of SpiderMonkey is
because
most people seem to have it in their distro already whereas V8 doesn't
seem
to be so prevelent yet.
The other issue with V8 is that it's a JIT engine, which restricts the OS
and CPU choices of the
Oct 25 2009 4:19am from davew @uncnsrd
Subject: Spider Monkey
I've been looking at the Spide Monkey documentation.
For simple apps that don't use threads it is self contained.
For multithreading apps like us we need NSPR as well so I guess thats
the
place to
Sat Oct 31 2009 03:56:12 PM EDT from IGnatius T Foobar @ Uncensored
Subject: Re: Spider Monkey
It uses it for everything, but it's optional for a single-threaded
parser?
How's that?
Are there any other JS parsers out there that we should be looking at?
Perhaps the KDE or
It uses it for everything, but it's optional for a single-threaded parser?
How's that?
Are there any other JS parsers out there that we should be looking at?
Perhaps the KDE or GNOME projects have their own?
I really don't want to add too many external dependencies, and I
Oh, here's a good starting point:
http://en.wikipedia.org/wiki/List_of_JavaScript_engines
Well, there's also the V8 JavaScript engine, which is what Chrome uses,
and is faster:
http://code.google.com/apis/v8/embed.html
