You can't do that in MicroPython!
summary
Claims concrete enough to act on: expect about 20–30% faster delivery versus C/C++ in real projects, with only small C hotspots needed; typical full MicroPython builds need around 200K flash and ~32K RAM but can be pared to ~40K flash by removing features or freezing code into firmware. Tools demonstrated include mpremote mount for live dev, MIP for libs, and C user modules. Wake overhead is ~15–40 ms and deep‑sleep vs Wi‑Fi draws ~1.5 mA vs ~120 mA, so battery use depends on sleep strategy.
AI-written summary · about
chapters (35)
- 0:00Intro
- 0:14Who is Matt
- 1:14What is a fullstack developer
- 1:27Audience participation questions
- 2:07What is a microcontroller
- 2:54Market size
- 3:19Reddit
- 3:36What is MicroPython
- 4:09BigPython
- 4:34Standard libraries
- 5:09Machine library
- 5:47Why MicroPython
- 8:45Junior developers become superpowers
- 9:32Performance matters
- 9:52Marketplace and slow
- 10:52Techniques for performance
- 11:28C Microphize
- 11:47Comparing MicroPythons
- 12:45Documentation
- 13:08Python to C
- 13:46Performance ceiling
- 14:04Microphone
- 14:45Temperature logging
- 15:06Power consumption
- 15:54Additional costs
- 17:07Key thing to do
- 17:43Porting effort
- 17:56Market demand
- 18:17microcontroller costs
- 18:48micropython requirements
- 19:55compilation
- 20:35workflow
- 21:16costs
- 22:53Summary
- 23:52Questions
