Nice ... not long ago someone mentioned 'having fun' as a good reason to use MicroPython. And see, here you have it.
Search found 39 matches
- Wed Mar 27, 2019 10:06 pm
- Forum: General Discussion and Questions
- Topic: Target audience for MicroPython?
- Replies: 63
- Views: 84382
Re: Target audience for MicroPython?
- Wed Mar 27, 2019 9:53 pm
- Forum: Programs, Libraries and Tools
- Topic: Pycopy, "Advanced MicroPython fork" by pfalcon
- Replies: 15
- Views: 18532
Re: Pycopy, "Advanced MicroPython fork" by pfalcon
If you choose to setup your own distro/community ... would it not be nice to find a name which actually makes you feel good about it? That tells something about your distro usp? Like Adafruit did with CiruitPython. They also copied the MicroPython project (hence, they also could have chosen PyCopy),...
- Wed Mar 27, 2019 9:26 pm
- Forum: General Discussion and Questions
- Topic: Target audience for MicroPython?
- Replies: 63
- Views: 84382
Re: Target audience for MicroPython?
Unless the thread objective is endless meta-discussion it might be helpful if you enumerated the "simple steps and decisions" you have in mind. It could be helpful indeed, but I've experienced oftentimes that it is very difficult to come up with a solution for non-existent problems. No one recogniz...
- Wed Mar 27, 2019 9:13 pm
- Forum: General Discussion and Questions
- Topic: Copyright statement
- Replies: 13
- Views: 11944
Re: Copyright statement
Ah, that indeed sounds logical. But what about the shared copyright statement in the documentation (more than one name)? Why is that, and ... does that last for long time too?
- Wed Mar 27, 2019 3:23 pm
- Forum: General Discussion and Questions
- Topic: Copyright statement
- Replies: 13
- Views: 11944
Re: Copyright statement
Well, I just dont understand and it seems odd. It seems to conflict with the MIT License. The copyright statement in the MIT License (as found in the root of the micropython repo) currently reads: 'Copyright (c) 2013, 2014 Damien P. George'. Should that not be updated to 'Copyright (c) 2013 - 2019 D...
- Tue Mar 26, 2019 10:54 am
- Forum: General Discussion and Questions
- Topic: Copyright statement
- Replies: 13
- Views: 11944
Copyright statement
At the bottom of the docs page on this url: http://docs.micropython.org/en/latest/
It mentions the following copyright statement ...
It mentions the following copyright statement ...
Is this correct? Anyone able to explain this?© Copyright 2014-2019, Damien P. George, Paul Sokolovsky, and contributors Last updated on 26 Mar 2019.
- Tue Mar 26, 2019 9:20 am
- Forum: General Discussion and Questions
- Topic: Target audience for MicroPython?
- Replies: 63
- Views: 84382
Re: Target audience for MicroPython?
@stijn
You are right. I rest my case. Everyones time is scarce ... mine too. Why bother ...
You are right. I rest my case. Everyones time is scarce ... mine too. Why bother ...
- Mon Mar 25, 2019 8:13 pm
- Forum: General Discussion and Questions
- Topic: Target audience for MicroPython?
- Replies: 63
- Views: 84382
Re: Target audience for MicroPython?
I don't think the problems for the no-firmware builders are difficult to solve. As long as the community wants it, and as long as the comunity does not dismiss every attempt with the 'minimal' dogma. I'm quite optimistic that with some simple steps and decisions, we can set out the path to make micr...
- Mon Mar 25, 2019 8:01 pm
- Forum: General Discussion and Questions
- Topic: fastest way to fill large bytearrays? (Neopixel, APA102 et al)
- Replies: 15
- Views: 33099
Re: Viper performance
The other take-away from these tests is the performance of Viper. A penalty relative to assembler of well under 2 is astounding. Perhaps the figures for the faster options are dominated by a fixed overhead in doing a function call. The Viper emmitter performance results are indeed very impressive ....
- Mon Mar 25, 2019 7:39 pm
- Forum: General Discussion and Questions
- Topic: How to include driver into micropython compilation
- Replies: 21
- Views: 66619
Re: How to include driver into micropython compilation
Would this problem be avoided if the wiznet5k drive was written in python? Or would that have been impossible?