Is the JS runtime complete?

[John Yeuk Hon Wong]

I was looking at the JS runtime according to https://developer.mozilla.org/en-US/docs/Zest/Zest_runtimes
Is it complete (4 months behind)?

Also, is there a reason to place the JS runtime in the Java runtime repo? Or is the engine itself is in Java? I am a bit confused the runtime and the engine in Java.

Thanks.

[Simon Bennetts]

Hi John,

We're actually still tweaking the Java runtime - we're working towards a new Zest release.
Once that has been finalised then I'd expect work on the JavaScript runtime to resume.

The Zest repo started out as the Java one, but its kind of morphed into covering JavaScript as well :)
We should probably tidy it up and have java, js and other runtime languages at the top level.

Cheers,

Simon

[John Yeuk Hon Wong]

Thanks Simon.
So I am thinking about writing a web fuzzer using ZEST (which we kinda of discussed when I was an intern). So is it correct to say runtime is essentially the engine? So I can implement a Python runtime or a Go runtime that reads in a ZEST script following the rules and semantics of ZEST.

Thanks.
John

[Simon Bennetts]

Yeah, the runtime and engine are synonymous (at least thats how I view them;).
I've been wondering if it would be useful to define different levels of Zest support - a simple engine which just runs basic requests should be straight-forward to implement and be pretty useful.
Adding support for all the other things (like complex conditionals) might take a bit longer, so having a graduated set of featured clearly defined might help? What do you think?

Let us know if you do decide to work on a Zest Runtime - we can then link you up with anyone else who wants to work on that language.
V happy for you to use the 'standard' repo or create your own.

Cheers,

Simon