3 ms·

Very interesting link, thanks! Shows very well viability and benefits of using Python on constrained systems. Using message passing for concurrent programming

by pfalcon 11y ago

Very interesting link, thanks! Shows very well viability and benefits of using Python on constrained systems. Using message passing for concurrent programming is a well-known technique, it's nice that they tested it in embedded Python context. However, regarding syntax extensions - I wished they run them thru python-ideas list. Because otherwise all the pattern matching can be done in Python already, perhaps with a little more syntax - well, the paper links to http://candygram.sourceforge.net/ http://candygram.sourceforge.net/ which implemented it 10+ years ago.

minthd 11y ago
Maybe there's a reason they implemented actors using extension ? performance/latency ? Maybe you guys should collaborate with the guys behind the paper ? they can offer their expertise - and if they built it inside micropython, that means many more people will use the technology - and they will get much more academic citations.
- pfalcon 11y ago
  I mostly refer to adding new syntax to the language (recv, pattern matching as described in that report). It's obvious why it was done - it's syntactic sugar which make programming easier. But it's no longer Python, a language many people know or run apps in. So I'd really like if embedded Python folks tried to run their ideas thru python-ideas list to get wider Python community feedback (and yep, we're trying to do our homework in that direction, and would hope to meet other embedded Python folks there). > Maybe you guys should collaborate with the guys behind the paper ? Definitely, I'm drafting a "Hello" email. And I think there's really opportunity for collaboration - they based Owl on PyMite, so I figure they don't fancy developing own VM from scratch, so if they'd be interested in Python3, here's MicroPython. And we could use feedback and wider discussion on topics of hardware access APIs. And prototyping various concurrency models for uPy would be just fantastic.

by pfalcon 11y ago

minthd 11y ago

Maybe there's a reason they implemented actors using extension ? performance/latency ? Maybe you guys should collaborate with the guys behind the paper ? they can offer their expertise - and if they built it inside micropython, that means many more people will use the technology - and they will get much more academic citations.

pfalcon 11y ago
I mostly refer to adding new syntax to the language (recv, pattern matching as described in that report). It's obvious why it was done - it's syntactic sugar which make programming easier. But it's no longer Python, a language many people know or run apps in. So I'd really like if embedded Python folks tried to run their ideas thru python-ideas list to get wider Python community feedback (and yep, we're trying to do our homework in that direction, and would hope to meet other embedded Python folks there). > Maybe you guys should collaborate with the guys behind the paper ? Definitely, I'm drafting a "Hello" email. And I think there's really opportunity for collaboration - they based Owl on PyMite, so I figure they don't fancy developing own VM from scratch, so if they'd be interested in Python3, here's MicroPython. And we could use feedback and wider discussion on topics of hardware access APIs. And prototyping various concurrency models for uPy would be just fantastic.