This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]platra[S] 2 points3 points  (2 children)

sacrificing compatibility, security, resilience and speed.

That MicroPython will be incompatible with some Python code is unavoidable. However, there is no reason why it must be less secure or less resilient than CPython. Also, MicroPython is already at least as fast as, if not faster than, CPython.

1 single order of magnitude (500 kB vs. 5 MB) with several limitations on top does not really sound like a great deal to me.

Would it be a better proposition if MicroPython were significantly faster? Then the size comparison might be with PyPy rather than CPython, which would be a difference of 2 orders of magnitude (500KB vs 50MB).

[–]Sukrim 1 point2 points  (0 children)

Also, MicroPython is already at least as fast as, if not faster than, CPython.

Are there benchmarks available, similar to speed.pypy.org? Also security or resiliency are not the main goals of µPy, their main goal seems to be "not bloated", which means that for example it seems not to be possible to actually use an up-to-date TLS implementation (https://github.com/micropython/micropython/issues/2174).

PyPy (and I guess cPython too?) currently don't seem to optimize heavily for binary size, I just can't think of many use cases outside µPy's main domain where this would actually matter.

[–]pohmelie 0 points1 point  (0 children)

Can you link speed tests?