svaarala

3 ms·

1. 1.▲
   by svaarala 8y ago

   By default Duktape maintains the built-in objects purely in RAM, but for low footprint targets the built-in objects (and also custom user objects) can be made pure ROM objects which reduces memory usage quite a bit; the lowest startup RAM u
2. 2.▲
   by svaarala 12y ago

   Very little performance work has been done so far. Most of the effort has been in E5 compliance and more recently to support low memory environments (96-128 kB system RAM) better. But there's going to be performance work early next yea
3. 3.▲
   by svaarala 12y ago

   These amount of flash/RAM are probably not realistic for a compliant engine. For instance, the Duktape regexp engine alone takes around 10kB flash compiled. Luckily Javascript has a great ecosystem, so there are non-compliant subset en
4. 4.▲
   by svaarala 12y ago

   Thanks! At the moment no, but send me an e-mail if you use Duktape somewhere :)
5. 5.▲
   by svaarala 12y ago

   Absolutely, the original motivation was to have a Lua-like implementation for Javascript.
6. 6.▲
   by svaarala 12y ago

   Around 200kB of code (flash), and around 25kB of RAM after startup, with low memory optimizations in the master branch (for the upcoming Duktape 1.1 release). This doesn't include User Javascript, just what Duktape needs to start up. Y