Not so sure it comes down to money, though it could boil down to resources not being spread so thinly. I'd suggest it could simply be a case of addressing what MicroPython hasn't cared to, and for marketing advantage.CircuitPython has a safe mode, probably they are not starving so much for money.
I don't use CircuitPython so it's not clear to me how well their 'catch it when it's gone wrong' solution works, how it actually determines when something has gone wrong or not, deals with something like a Pico W web server which could quite reasonably be waiting for a web page request for hours or days at a time, forever if something internal or external has failed or gone AWOL.
It may be great but it all seemed a little too complicated for me when all most people want is a means to boot into a REPL without running their incorrect 'main.py' which locks things up and prevents that, has to be solved by Nuking the Flash.
If something based on USB serial baud rate were added to MicroPython that would allow Thonny 'stop' to force it back the REPL under nearly all circumstances. The same protocol can be used from the command line, in VS Code and other IDE.
I think there's even mileage in allowing Ctrl-C to force a return to REPL in all cases unless that is explicitly disabled. The issue mostly boils down to not being able to stop some 'main.py' once it has started.
Statistics: Posted by hippy — Wed Jan 15, 2025 9:38 pm