Just because the code is open source doesn't mean there's no usage
restrictions in what you can do with it. Most open source licenses
take a dim view of using open source code in closed source commercial
software, as there's always a risk that if it was allowed then the
commercial organization
I just randomly came across this Ajaxian podcast episode from a while back
that answers the very question I posed.
http://ajaxian.com/archives/audible-ajax-episode-20-project-tamarin
Interestingly, Adobe open-sourced their JIT implementation of Javascript
after a 3 year complete rewrite, and
On Oct 1, 11:51 pm, Derek Gathright [EMAIL PROTECTED] wrote:
... With Firefox 3 having SQLite
(rumored) embedded and Google releasing Gears, the capabilities are endless
for developers using the browser as the platform/OS for on and offline
applications. That is going to require much more
On Mon, 2007-10-01 at 16:46 -0700, John Beppu wrote:
http://ejohn.org/blog/javascript-engine-speeds/
Very interesting! I have been using rhino for a week or so. When I
started looking at the results, it was very disappointing. Then I got to
the real world examples. Why does rhino shine there
Thanks for the link, interesting stuff.
After looking through info on Rhino, I was left with the question... why
build the JS core engine in Java and not a non-interpreted language? Then I
looked at info in Spidermonkey (a C re-write for Firefox 3) and saw they
realized the same thing.
http://ejohn.org/blog/javascript-engine-speeds/
6 matches
Mail list logo
