Comment by self

15 days ago

Think of it as a runtime + scheduler that you deploy programs to ESP32 devices. It gives you the ability to run multiple programs simultaneously (with isolation) and remote updates. The language compiles to bytecode; the developers have lots of experience writing VMs for constrained devices; see https://www.theregister.com/software/2004/07/27/forgotten-la... for something that predates V8 and Dart.

You get almost all of that with the more common language options too (MicroPython, NodeMCU/Lua, Espruino/JS). What makes this custom language better?

  • We looked at these when we started. The problem with them is that they weren't designed with constrained resources in mind and it shows. For example, objects are hash tables and method calls are thus expensive. An obligatory top level execution makes startup slow, ...

    If you have a bigger machine you can optimize some of this (V8), but these optimizations typically need memory and/or a JIT. (And Python struggles to optimize even on stronger machines).

    By starting from scratch (with what we learned from V8 and Dart) you can design something that feels similar but is much cleaner and faster to run.

    • Those requirements are at odds with each other though. If you want to get the most out of MCU hardware you typically use C/C++/Rust, either as a whole or via a custom build of MicroPython/NodeMCU/Espruino. MicroPython has some interesting options for high performance code that you (optionally) run on your PC before deployment.

      Besides that, there are other languages that have similar characteristics. Wren (https://wren.io/) is pretty nice but doesn't have type annotations or explicitly target embedded.

Thanks! This should be on the homepage IMO instead of the AI slop (or human slop? not sure) that's there now.

This looks super useful actually, I worked in embedded systems in the past and the choice was either go with a microcontroller and have like no features, or do a full Linux and have (much more expensive hardware and) half the team distracted by doing proper linux app development and networking and all that stuff that comes with it. Often we chose plain C microcontroller simply so the team wouldn't go overboard designing a multi-node distributed system when all we needed was control a couple sensors and actuators, but it lacked exactly what you describe, concurrently running multiple things and easy updates. Ok, and printf, which I'm going to blatantly assume is covered here as well.

So yeah this sounds super nice!