This is increasingly a false choice.
If you use node.js, you have both JavaScript and native modules.
Use JavaScript for the non performance critical parts, use C for the parts that touch the hardware, and leverage the great node ecosystem.
If you use node.js, you have both JavaScript and native modules.
Use JavaScript for the non performance critical parts, use C for the parts that touch the hardware, and leverage the great node ecosystem.
Power consumption and, to some extent, board size have been very significant drags for the Internet of Everything. Mindlessly throwing libraries at them just to help people who are too lazy to learn a new programming technology is only adding a drag on it.
I certainly don't want to drag this into the mud. It's certainly a good learning platform which can provide exposure to a range of devices for people who would otherwise not even hear about them, or for whom the initial technological barriers would be too high to overcome in a single evening. But this is far, far from adding any kind of value to the struggle towards universal Internet connection.
Embedded dev is all about performances, power consumption ,etc ... it is about focusing on hardware , not about how much libraries you can throw at a problem, since you usually do not throw any,because of limited memory, computation power...