Professionals need better tools than amateurs like 16yo schoolgirls, since they have time constraints and get paid to make stuff quickly and cleanly (not quickly and dirty ).
And as for "dirty" ... I have stuff running here (on the Arduino) in this house. It runs for months without rebooting. It works, and works perfectly. I would not characterize it as "dirty".
We mustn't lose sight of Arduino's provenance and original purpose, which (at least as I see it) was to let a bunch of lay folk write code and get it into a processor in a bit of a quick-n-dirty way so they could make stuff happen in the real world.
Why only months? Isn't it reliable?I'm not being cheeky, just wondering.
By the late 80's gdb was already fully working in many embedded environments
I guess they've pretty much always had debuggers as well.
But for more serious development I'd prefer full debugging capabilities.
My early programming was for British Shipbuilding (Vosper Thornycroft), using COBOL/CICS/DL1. There was very little scope for debugging tools on System 360/370, so it was all about watching what came out for what went in, and ploughing through dump listing.