However like any other open source system, the bugs are being detected and cleaned up.
And I appreciate the incredible efforts - what an amazing concept. You gotta wonder about the priority system though. The only high priority one on the list last night was to give a more informative error message in some situation. In this case the system falls over. But it's not polite to quibble over a gift, so I wont.
I would suggest for something like a kiln, whether it is an Arduino or some other device, you not have a single point of failure. So for example, a thermostat or something as a secondary backup.
For a potential fire hazard such as a kiln, in my mind this calls for a system design which does not have a single point of failure.
Thanks for the reality check, guys. I'll try and find another thread for continuing this point.
it's not a very apt analogy
Analogies are like Strings: they break down sooner or later.
anyone with much experience working with memory restricted microprocessors knows that using dynamic memory allocation is just a bad idea, period. Since Strings use dynamic memory allocation, nobody with much experience uses them, hence why the bug is receiving little attention.
You're obviously right, but the logic escapes me: it's a high impact problem that's been around a long time, everyone knows about it, so we're not in any rush to fix it. I love it - like something out of Catch 22.
In my view, its nothing more than a booby trap for novices.
Here here. Who decides what goes on the Reference page of the Arduino site?? I'd like a word.
Thanks all for all your responses. I'm off to sanitize my programme. I may be some time.