3 ms·
Very nice, I wish this were around when I was writing my A6 lib: https://github.com/skorokithakis/A6lib https://github.com/skorokithakis/A6lib Hopefully the M
by StavrosK 9y ago
Very nice, I wish this were around when I was writing my A6 lib:
https://github.com/skorokithakis/A6lib https://github.com/skorokithakis/A6lib
Hopefully the MicroPython ecosystem will expand with efforts like this one, how did you find performance? I'm always worried about memory usage with μPython.
- deleted 9y ago[deleted]
- rollcat 9y agoBased on the hearsay, µp actually has much better memory usage than CPython (but obviously worse than C). Considering it's striking a pretty nice balance between high-level features and low overhead, I'd say it might be worth it, especially if you're aiming at a very hackable phone. This is definitely going on my "list of things to do when I have too much time".
- SEJeff 9y agoIt isn't really heresay. You can run µp on systems such as an esp8266, which you couldn't run cpython on. It does run, but lacks much of stdlib (by default).
- dbcurtis 9y agoWell, you don't need to fall back on hearsay. The code is on github. It is a good read. Micropython is, in fact, extremely parsimonious with memory in it's native state, and you have reasonable options to get even tighter if you like, at the expense of portability. As it is, most of Micropython's portability quirks come from trading off 100% CPython compatibility to achieve a small SRAM footprint. Micropython byte code is not particularly fast in an absolute sense, but is very good all things considered in the context of a microcontroller. I find for really performance critical stuff a few lines of inline asm (which Micropython supports natively) often is sufficient. And for the rest, a C module is always an option.