4 ms·

The first statement is not true. Web developers use debuggers for front and back-end work just as much as anyone else. It's probably why Chrome and its develope

• vardump 10y ago
  Those tools that help with distributed messaging are logging or sugar coated logging. Logging can be a part of a debugger, but it's not the core reason why debuggers are used. Usually "debugger" refers to running a controlled portion of a program, to some specific position is reached (breakpoints, stepping) or until something in program state is true. When the condition is met, the debugger suspends execution. Debuggers also offer ability to inspect program state. Chrome developer tools can do request logging. It can log the HTTP requests, timelines, Javascript console, etc. It also contains debugging tools for Javascript, but those are rather unlikely to help with debugging distributed messaging.
  • ctvo 10y ago
    We must be talking about two different audiences then, because web development in my experience has little to do with distributed messaging. Most web developers work in JS for the front-end -- they use Chrome to debug client behavior. Most also write the layer in the back-end that communicate with databases and other data sources and handle business logic. They use debuggers for their language to follow program flow and inspect values. Once their layer needs to communicate with other systems or do anything with distributed messaging, their responsibility ends and the need to debug the issues of the other systems becomes someone else's problem.