BertB wrote: ↑19 Sep 2017, 19:50
Now this is not necessarily true, is it?
I mean, it is often so that development on older technologies grinds to a halt, when a new development gains in popularity.
I do not need the muscle power to swich a light or to tell me the temperature in the garden.
So yeah, this tendency worries me a bit. I have spend a lot of time and money creating stuff with ESPEasy and to be honest, I hate the thought that it will all be lost.
Don't worry, the Py version will run on the same hardware (well maybe not the 512KB version, since that's not supported by uPy).
The Py version will be portable, enabling a lot more platforms. You can make it as simple or complex as you want, the reason for the Py version is flexibility...
I'm developing it on a fast ubuntu server since the dev cycle is soooooo much faster then on a soc. I can develop, test and develop in just seconds on ubuntu, the server does a complete make build and run in just below 10 seconds, compared to hours on a soc (building firmware, loading it on a nodemcu, test it, find little debug info, etc). On ubuntu the image size of micropython with frozen modules is currently just 433KB, plenty of room left!
The dev hardware cycle is: ubuntu -> pyboard -> nodemcu -> Esp01 (with 1MB+)
I also have a few sonoff module's i don't want to lose, it's in my own interest to keep supporting smaller soc's...