We've been listening to thousands of sources of information (which, besides users also includes experience and history of other projects, research results and considerations how to address millions of usecases) for 3+ years, no worries on that side.
So, now question from me - when you start to listen to what you're being told?
From the earlier post of this thread:
If .on/.off doesn't work for you, no problem, use .value(). Want something else - no problem, it's Python, so everything is easy. Subclass Pin or wrap it and add whatever you want.
How MicroPython is designed is that we take the barest minimum to let something be done. In case of Pin, it's Pin.value(). Then we see if adding 1 (one) another piece of functionality may extend usecases noticeably (say, 2x). If so, we add those, in case of Pin and Signal, that .on() and .off() (yeah, one for each
). Everything else, is covered by its majesty Python, and is to be done by users by their needs. That's how MicroPython has always been, continues to be, and how its going to grow to even higher heights.
I'm definitely sorry to hear that you
don't like that. Everyone else, can rejoice that now we finally have the foundation of hardware API - basic GPIO operations - defined, and can proceed to develop great, now fully portable MicroPython applications.