Comment Re: Why? (Score 3, Insightful) 45
Not sure I see the cost argument? I don't think I ever paid more than $15 for a breadboard. An interpreted language on a microcontroller requires too much suspension of disbelief, especially when learning a more embedded-appropriate language requires only marginal additional effort. Trying to run JavaScript on an MCU would be equally silly and for the same reason. Shoehorning python onto an embedded system creates the "illusion" of a simple language, while casually glossing over the _real_ aspects of embedded systems, like resource management, memory allocation, and a limited runtime environment. No amount of window dressing and training wheels will change the fact that programming these systems is fundamentally different from how any sane person normally uses Python. Yes, you could create some 'bridge features' to try to make this easier, but then you end up with a hodgepodge of intermingled concepts that were never meant to go together. This confounds the learning process.