2 ms·
A debugger is something that has to be developed. Printing is for the most case already there. It's not always the case if you like the one or the other. With
by marto1 5y ago
A debugger is something that has to be developed.
Printing is for the most case already there.
It's not always the case if you like the one or the other. With out of the ordinary issues or places where you can't afford to sacrifice performance but still would like to have some insight printing usually wins by a large margin.
- ehnto 5y agoRight, but that's a choice someone has made. You or someone has decided "I am going to build or use tools that can't be debugged". We should be at a point of maturity in software tooling where that never happens, at least for commercial software companies. I don't much mind what anyone uses in the free time or on their solo SaaS, but as service providers we should be aiming to use mature and effective tooling. I'm not sure what you mean about performance, since debugging is something you should be doing once off in a local development environment, it shouldn't impact performance for users. Even videogame engines can be debugged. If you've got an issue only happening in production, you should probably try and replicate the production environment so you can debug it locally instead of messing about in prod.