You are reading a single comment by @allObjects and its replies. Click here to read the full conversation.
  • Having reviewed earlier the specs, I see quite some potential in this 2 core setting. Foremost it gives relieve on the issue of the 3 main tasks on single core:

    1. wifi/communication
    2. Local (sensor) low level hardware/appliances/port event handling,
    3. js execution

    Integration of latter two is already included in Espruino, which makes it just a 2 main tasks operation and a good match for 2 cores.

    Having more resources available - memory and cycles - is convenient for application development but is heading in a different direction as Espruino - at least - for the past was - and still is - going for: smaller and less power demanding at runtime (even though it included some memory increase).

    Wifi always needs significant power, one can say... but the new Espruino Wifi alreadt provides both wifi and low power Espruino in a decoupled way. The new ESP32 device can not go that frugal.

    Giving ESP32 a shot and see where it leads to is for sure worth a try... and should even include a slimming down of the ESP32 infrastructure (OS) to a minimum in favor of 'the Espruino side' of the overall implementation. Latter would at least stay true to the original spirit of Espruino: keep it simple and easy to use, all through JS!

About

Avatar for allObjects @allObjects started