Ommm... devs, align your Chakra, whispers Microsoft, you don't need Google's V8...

running node on Win10 IoT Core - oh god, please, no!

currently working on a project for a client which requires running an existing node.js headless app on an IoT device. Because it currently runs on a tiny footprint PC (running "regular" Win10 and vanilla v8 node) they thought porting it over to Win10 IoT Core on a Raspberry Pi B would be a no-brainer... until we discovered that you have to install Visual Studio, add a bunch of extra tools to it, jump through hoops to make the device work and talk to the PC, migrate your project into a Universal Windows Node Server template (along the way forking the app so I hope that's where you want to be) and then... try and run it on the device at which point it all falls over in a heap with no error messages.... three days down the drain.

Switch to plan B which it install Raspbian, vanilla node, copy the files onto the SD card, SSH into the machine and run "node server-main.js" and ... that took less than 3 hours.

If anyone has had more success - getting a Win10 IoT Core machine with node up and running (and able to watch the console when the app runs) - please... share your wisdom!

fragmentation?

So in theory it is nice that node can support multiple JS engines, but in practice it means that developers now also need to test their server-side code on all engines. Or, more likely, only test on the one engine on which they actually deploy. Leading to "this code tested on Chakra only", or "this code tested on V8 only", in other words: fragmentation of the node ecosystem.