这几天，在MicroPython官方论坛上，发起了关于MicroPython是否可以真正用在产品开发上（Is MicroPython ready for real world deployment）的讨论，非常有趣。我觉得值得大家看看，所以简单的翻译和整理了一下。
If I wanted to deploy a large number of devices and have them run reliably, would MicroPython be a risky choice?
We are using Micropython in several projects (medical & industrial certified measurement equipment) for ~2 years. It was a bold decision, but it already paid off.
don't the other benefits exist for C/C++ (with or without an widely used OS/RTOS) ? e.g. clang or gcc, FreeRTOS, etc?
MPY outperforms all the tools we know (even the ones we can't afford) for our application portfolio and a broad range of different MCU types. We came to MPY while searching for a lightweight python implementation for a linux based system to get rid of bloated shell scripts.
For this first project it ended up with getting rid of linux replacing it with MPY. Two years later we cover ultra low power systems (consuming 500nA with active REPL!) to real-time image processing, all with just one development and runtime environment.
I'd say problems with the uPy side of things are extremely rare and the API is also very stable, and even if there is a bug or feature missing the fix takes a couple of days at most (either fix by main devs or time to get PR merged).
Frankly I don't think there are many other scripting language implementations out there that work as good for the pros mentioned by chuckbook already.
Lua is ok but it's not Python. CPython works but good luck getting it to compile on non-pc or embedded pc hardware. Or trying to understand the code. C and C++ are tried and tested and pretty awesome if yo know how to use them properly, but are not scripting languages at all.