News for hackers. Stuff that matters.
Re:Microsoft DeviceScript – TypeScript for Tiny IoT Devices by TheLoafOfBread on Friday June 09, 2023 @10:05AM (#36257985)
You are completely missing my point. When I have C code and compile it, I will have opcodes which processor can run. All my bugs are going to happen only in C code and I can debug those using one debugging probe.

When I have embedded scripting, then I have C code which represents my VM and I have also scripts. Then I am hunting for a bug in C code and script itself. I need two debugging stacks to get the problem solved. Sure you can say that I can run scripts on my PC, but what if everything works on my PC, but the moment I will load it on the target, script will crash? Then without proper debugger I am screwed.

Re:Microsoft DeviceScript – TypeScript for Tiny IoT Devices by mmoskal on Friday June 09, 2023 @10:34AM (#36258417)
DeviceScript comes with a source-level debugger for the VM code.

Indeed, if you add C code and that crashes it maybe harder to debug than a pure C system, however it wasn't my experience while developing DeviceScript - it was either clearly a bug in C that didn't really depend much on the bytecode, or an exception in DeviceScript which you debug just like in TypeScript.

We also support Jacdac [0] which makes it possible to put the C code on a different MCU, isolating the problem and adding traceability. (You can also run Jacdac server on the same MCU)

[0] https://microsoft.github.io/jacdac-docs/

Re:Microsoft DeviceScript – TypeScript for Tiny IoT Devices by HumanOstrich on Saturday June 10, 2023 @11:26PM (#36277698)
I appreciate your engagement throughout this post, including how you are gently educating the naysayers.