4 ms·
When engineers start cutting corners and start to design not for performance but “speed of development” — it becomes a slippery slope. I guess I’m speaking fro
by ak_25 6y ago
When engineers start cutting corners and start to design not for performance but “speed of development” — it becomes a slippery slope.
I guess I’m speaking from the standpoint of a firmware engineer, I honestly don’t think going with micro-python for our next product will buy us anything.
However, as I said; if you’re not into firmware and/or just getting started, this makes a great prototyping language.
- StavrosK 6y agoIf you're a firmware engineer and already familiar with the ins and outs of C, I don't think it buys you anything, agreed. I also don't think there's something fundamentally wrong with it that would force a hobbyist to rewrite everything in C if they wanted to commercialize their prototype.
- ak_25 6y agoI can agree with this. If you find a language that is more approachable and gets stuff done, you should go for it. (And hopefully get sucked into firmware(I wish we had more firmware-engineers ;-) ))
- pjmlp 6y agoFor me, some of the hardware supported by MicroPython is more powerful that what I had on a desk during my MS-DOS days, so I can easily see using it for certain kinds of applications. If it was good enough to run Turbo Basic, Quick Basic, Turbo Pascal, Turbo C++, Clipper, it can easily take MicroPython.
- schwartzworld 6y agoyou're being a little hyperbolic. haven't you ever heard of premature optimization?