Not logged in

Origins of Jsi

Jsi originally derives from the javascript interpreter quad-wheel.

Although not much of the original source code remains (Jsi is about 5 times larger) ancestry can be seen in the parser, eval-engine and test suite.

Jsi is a C-centric, byte-code interpreted focused on embedded development.

This makes it very different from Node-js, a C++-centric compiler that is non-trivial to embed.

Internally Jsi is modelled after Tcl.

A Glue Language

Like Tcl, Jsi is meant to be a glue language.

This means that time/space critical functionality is implemented in C, which scripting glues together:

Testing is one example where efficiency is less important (eg. Sqlite Testing) and glue code can be helpful.

ECMA Compatibilty

Jsi implements most of Ecma-script 262, version 5.1.

Following are the known omissions:

Additions include:


Following are the primary goals of Jsi:

Note: C-integration is the main priority, not script execution speed. The C++ compile option is mostly for integrity checking.


Following is a partial list of things that are either incomplete or unimplemented: