You are reading a single comment by @DanTheMan827 and its replies. Click here to read the full conversation.
  • Yeah, basically just having the entire editor be C with the nrf calls directly accessible, essentially main.c

    perhaps to keep things a little easier, have the firmware call a loop method.

    Something similar to the arduino IDE where you have main and loop methods and those are called from a lower level

    you could still have the firmware handle all the existing loop logic to keep all the RF and running, but then it would call the loop method of the IDE code directly

    the console could be bound to something like the Serial module from arduino, and for re-programming from the IDE, or accessing files, you could momentarily skip processing the loop call.

    really just an advanced mode more-less that presents lower level functionality and performance with the ease of the web ide.

    inline c is nice, but it ultimately is only as fast as the time it takes to go from the javascript interpreter to the native module, and if you're doing something that requires a lot of performance javascript isn't always the best, but setting up the toolchain and going for a full firmware is a bit more difficult than the web ide.

    The hardware has potential, but the javascript interpreter slows things down considerably, yet the web IDE is one if the selling points of the hardware

About