> MicroPython officially becomes part of the Arduino ecosystem<p>sounds like an acquisition, but<p>> Expanding on this initial experience we were lucky enough to partner with the creator of MicroPython, Damien George, to port the official the virtual machine to a number of Arduino products.<p>and<p>> Luckily we came across the work of Murilo Polese, who developed a simple tool we were able to adapt and use for teaching. The results have been so good that we decided to collaborate with him to produce a tool we can share with the community.<p>just sounds like they're heavy <i>users</i> - and contributors, to be fair - of micropython. Anyone have a better idea of what the relationship is?<p>EDIT: A quick look at <a href="https://micropython.org/" rel="nofollow">https://micropython.org/</a> shows them still leading with the "pyboard" as their official hardware that they'd like to sell you, so I'm leaning towards "partnership" rather than "acquisition". Can't imagine that Arduino would do anything but immediately start pushing their own hardware.
I'm curious if embedded scripting language gurus know, would micro-python be suitable for pico-8? I'd prefer python over lua about 100 to 1. But maybe even in micro form, python is still too big to embed in that project?
I'm going to be using this because it's in theory it's much easier to have over the air updates when the business logic are just text files, rather than compiled binaries.
Thonny has MicroPython support.<p>"BLD: Install thonny with conda and/or mamba"
<a href="https://github.com/thonny/thonny/issues/2181" rel="nofollow">https://github.com/thonny/thonny/issues/2181</a><p>Mu editor has MicroPython support: <a href="https://codewith.mu/" rel="nofollow">https://codewith.mu/</a><p>For VSCode, there are a number of extensions for CircuitPython and MicroPython:<p>joedevivo.vscode-circuitpython
<a href="https://marketplace.visualstudio.com/items?itemName=joedevivo.vscode-circuitpython" rel="nofollow">https://marketplace.visualstudio.com/items?itemName=joedeviv...</a><p>Pymakr
<a href="https://github.com/pycom/pymakr-vsc/blob/next/GET_STARTED.md" rel="nofollow">https://github.com/pycom/pymakr-vsc/blob/next/GET_STARTED.md</a><p>Pico-Go: <a href="https://github.com/cpwood/Pico-Go" rel="nofollow">https://github.com/cpwood/Pico-Go</a><p>/? CircuitPython MicroPython: <a href="https://www.google.com/search?q=circuitpython+micropython" rel="nofollow">https://www.google.com/search?q=circuitpython+micropython</a><p>Aurdino IDE now has support for Raspberry Pi Pico.<p>arduino-pico: <a href="https://arduino-pico.readthedocs.io/en/latest/index.html" rel="nofollow">https://arduino-pico.readthedocs.io/en/latest/index.html</a><p>Rshell and ampy are CLI tools for MicroPython:<p>rshell: <a href="https://github.com/dhylands/rshell" rel="nofollow">https://github.com/dhylands/rshell</a><p>ampy: <a href="https://github.com/scientifichackers/ampy" rel="nofollow">https://github.com/scientifichackers/ampy</a><p>Fedora MicroPython docs: <a href="https://developer.fedoraproject.org/tech/languages/python/micropython.html" rel="nofollow">https://developer.fedoraproject.org/tech/languages/python/mi...</a><p>awesome-micropython: <a href="https://github.com/mcauser/awesome-micropython#ides" rel="nofollow">https://github.com/mcauser/awesome-micropython#ides</a><p>awesome-arduino: <a href="https://github.com/Lembed/Awesome-arduino" rel="nofollow">https://github.com/Lembed/Awesome-arduino</a><p>KiCad (ngspice) is an open source tool for circuit simulation. Tinkercad is another.<p>TIL about Mecanum wheels.<p>wokwi/rp2040js:
<a href="https://github.com/wokwi/rp2040js" rel="nofollow">https://github.com/wokwi/rp2040js</a>:<p>> <i>Raspberry Pi Pico Emulator for the Wokwi Simulation Platform. It blinks, runs Arduino code, and even the MicroPython REPL!</i><p>What are some advantages of Arduino IDE? (which is cross-platform and now supports MicroPython and Pi Pico W (a $6 IC with MicroUSB and a pinout spec))
It might be odd but I find Python so disrespectful to embedded devices. It pains me to think of all of the excess work those tiny things will do forever because of a very poor language choice.<p>More seriously, I think the long term effect of this will be truly catastrophic. There is an unfortunate effect whereby a tool's simplicity is able to attract newcomers to the space - which is great - but then severely limits progress by boxing them into this very small, simple, framework. It's very awkward when smart people and even professionals spend a lot of time fighting against the simplicity of Arduino or using weird, esoteric hacks as if it makes them a guru, just because it's all they know.<p>There needs to be an offramp. Micropython is the opposite - it's a one-way freeway to the middle of nowhere. It should be banished. So much human potential will be capped and wasted by this move.