@Theol I like the way you're thinking, trying to make things affordable easing coding life for noobs, not so easy task.
Imho I prefer non blocking stuff too, state machine like. I think this is really the way to think for a machine, IOT.
I think this is kind of education..more mcu programming related.
A very basic state machine just needs few "If" and/or "switch case". Often, people don't know theyr're doing a state machine I mean the basics of course, because you can use function pointers etc which are more advanced, use more mem etc..I choose function pointers or "If/switch" depending of the context but looks better with pointers. I hope I don't say dumb things or Yveaux will correct me
Ideally, very basic and important stuff a newbie need to learn for playing with a MCU, then with Mysensors, would be:
to understand why there is no "multitask" regarding how an mcu works. and irq, priority and pullup/downs..
a bit of algo
and arduino reference..
Sure Mysensors looks easy to use. And that's true
But if people think they don't need to learn this, even with multiple override, they will be limited, with more bugs, and more questions.. Then, of course, newbie would be happy to have done something, so he shares (thx). And an other noob comes, takes the sketch and share etc. finally where's quality..
I have rarely seen this (about delay) when i was learning from microchip community though And that's what I thought first time I saw arduino community! What this..so much people are using delay here! I will have to write my things from scratch, I can't trust, I will have not time to check everything..damn! Hopefully that's not completely true!
Have they read some reference before starting? With all resources from arduino, I think there is no excuse Led blinking without delays etc..
Hmm, a bit philosophical..Vulgarisation, mastering I understand main Mysensors goals. Why not a graphical ui in place, which would use "blocks" instead of code?
I'm always interested with your stuff @Theol and will keep an eye on this too