4 ms·
Write once/run anywhere would be a motivation. By the looks of it you wouldn't be able to literally run just any script on the chips that you bring over from a
by coderdude 16y ago
Write once/run anywhere would be a motivation. By the looks of it you wouldn't be able to literally run just any script on the chips that you bring over from a desktop machine, but the amount of tweaking would be minimal I think.
Being able to use Python's standard library on a chip would be useful. It's a dynamic language so you can do things you couldn't do with C. It's type-safe and easy as all hell to use. The usual motivations for using Python apply here. It just uses more resources and is understandably slower to execute.
- viraptor 16y agoSome objections: Write once/run anywhere would be a motivation. - "Run anywhere" is not true for most desktop programs and definitely not true for embedded stuff. When you're at 64k, you usually don't even reuse stuff like display handling, because your PCB layout is different enough that you'd have to rewrite the i/o layer anyways. Or because you a specific way to get the data. Or... I can't imagine much reasonable code reuse outside of standardised platforms like Arduino. Much less any "run anywhere" programs. It's a dynamic language so you can do things you couldn't do with C - There's nothing in language X, that you cannot do in C. Since it seems to be a google project, I guess they're just trying to create something that can be pushed onto Android, much like their own Java VM.