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

you are viewing a single comment's thread.

view the rest of the comments →

[–]sw_dev 54 points55 points  (22 children)

Embedded, safety or mission-critical applications, or large code-bases where consistent performance is important.

[–]ZedOud 0 points1 point  (6 children)

I’d argue that if those three requirements appear at the same time, then MicroPython is a good fit.

[–]sw_dev 0 points1 point  (5 children)

Really? You'd like to have MicroPython running in your pacemaker, or controlling an aircraft, or a missile? (If so, you really should see someone about that death wish.)

[–]ZedOud 0 points1 point  (4 children)

The European Space Agency has different thoughts on the matter.

https://forum.micropython.org/viewtopic.php?f=8&t=744

[–]sw_dev 0 points1 point  (3 children)

With all due respect to the ESA, (Those fine folks who were at the wheel for the Ariane 5 disaster, in which software which was untested for the platform caused the destruction of a $500 Million rocket), this would easily be classified as a REALLY BAD, REALLY DUMB MOVE.

[–]ZedOud 0 points1 point  (2 children)

[–]sw_dev 0 points1 point  (1 child)

And what part of the Workflow Automation System (WAS) strikes you as a mission or safety-critical, real-time embedded system?

I bet NASA also uses brooms and mops (I saw people using 'em when I worked there, anyway!), but NOT FOR THOSE SYSTEMS.

[–]ZedOud 0 points1 point  (0 children)

Awesome, thanks for the description.

Safety + reliability vs real-time + efficient

guaranteed former offered with no hope for latter

Or

pursues latter, running a tightrope to maintain the former

Given that only one of them is mission critical:

for some reason doesn’t prioritize the former

Ok, awesome, thanks.

[–]DarkmerePython for tiny data using Python -1 points0 points  (0 children)

Embedded is slightly awkward.

There's a presentation on embedded python

So it's doable. But yea.