This project has moved and is read-only. For the latest updates, please go here.

Is Jurrassic Dead?

Sep 20, 2013 at 9:20 PM
Soon it will be three years without a release. Just wondering if there is any more development going on. I'm looking at either Jurrassic or Javascript.Net which is built on Google's V8 Chrome engine,

I really like the flexibility of Jurrassic but don't want to start a new project on a dead system.
Sep 29, 2013 at 9:30 PM
It's more or less dead; but the author is still very much active. I was able to get him to make some changes recently. :) So I'd say use it; it's really good and if you have questions he'll still answer them. And who knows, perhaps a few more bugs might get fixed?
Sep 30, 2013 at 11:14 AM
This project is currently in "maintenance mode" - I will still fix bugs as they are reported, but that is all. At some point (hopefully soon), I'll do a 2.2 release to package up all the (dozen or so) minor bug fixes that have accumulated in the last few years. I would like to implement ES6 as well, once the spec has stabilized (which will probably be around Christmas) but I have a couple of other projects which are keeping me busy so no promises.
Nov 17, 2013 at 4:49 PM
Edited Nov 17, 2013 at 4:50 PM
Jurassic is pretty much the reference of embedding JavaScript in a C#/.NET application on Windows, because of high degree of interoperability between the C# and JavaScript world. And the other JavaScript runtimes implementation like jint or have been abandoned. IronJS is completely rewritten from F# to C# and there is no delivery date.

It would great for the .NET community to keep Jurassic alive and ES6 compliant?
Ask for help if you need it, to continue on Jurassic?

Regarding interoperability, I recently wrote 2 blog posts about: Scripting a C# application with JavaScript and Jurassic.