You need a lot more expertise to use an asynchronous programming model. It is much simpler to just busy loop with timed waits. If micropython is going to be easily accessible it needs to support the old school BSD socket API. Beginners and non professional developers want to be able to cut and from other peoples network code and have it work.<p>100% it is a downgrade. Every experienced developer knows the async model is more performant, at the cost of complexity. My micropython fork is super quick and super stable, it&#x27;s just not easy to use for beginners. For the ESP micropython port to succeed they need to create groundswell of people using the more compatible APIs. Until now, with the cost of the board subsidising the development there has not been much motivation to even put even posted bug fixes into the port. Using the kickstarter and maybe more community support will maybe bring the ESP port up to a first class citizen.<p>Personally, my port is a hell of a lot of fun to work with and async is a total win on this board.<p>This model is certainly more modern and works <i>way</i> better than a for loop<p>def hello():
  print(&quot;hello&quot;)<p>esp.os_timer(callback=hello, period=1000)<p>But, it&#x27;s not compatible.