This is my project/blog post and yes, I've gotten that feedback a couple of times. I mostly work in control systems and probably reflexively think narrowly about that context. But it's definitely tailored to controls - I wasn't intentionally trying to oversell it or anything.
(Side note: While running Python itself on a microcontroller is growing in popularity for educational and hobby applications, there’s no real future for pure Python in real-time mission-critical deployments.)
Bridging the two could be a real win for people using hardware like the M5Stack ecosystem, which has a wealth of peripherals and a robust Python stack.
So it's software to write firmware, not software to design hardware. Not sure how ambiguous that was to others but I got the wrong impression from the title.
Are the 50 for loops truly necessary in the manual C code example of a Kalman filter? At least introduce a few functions (that could be inlined and loop-fused) for some matrix operations?
9 comments
[ 2.5 ms ] story [ 26.4 ms ] threadhardware engineering is a very broad field and the title is misleading
Oh well I guess the Archimedes wasn’t that we’ll known.
Bridging the two could be a real win for people using hardware like the M5Stack ecosystem, which has a wealth of peripherals and a robust Python stack.