I've done a lot of debugging on Python, Java and C++ over the years and never felt like I was missing tools (although I certainly met plenty of people that were ignorant of their options in this regard...)
I've done a lot of debugging on Python, Java and C++ over the years and never felt like I was missing tools (although I certainly met plenty of people that were ignorant of their options in this regard...)
Since on a more open platform like the CLR, JVM Python interpreter or bare metal (as opposed to a controlled sandbox like the browser) there are many different network traffic libraries dealing with all kinds of different ways of communicating (everything from basic HTTP to binary protocols for communicating with hardware like DNP3).
How would the standard debugger hook into all these different libraries? I'm assuming they'd have to implement hooks and maintain them too, nevermind if there's more than one debugger available to be supported.
Seems like a lot of effort compared to just using a tool like Wireshark or, for HTTP stuff, a MITM proxy...
For the same reason it doesn't seem that useful to bring in very environment-specific stuff like Redux.
I had an example for Redux, because one of my pain is that there is no larger view framework for Java, which can’t access JNDI. In other words, nothing stops anybody to create something like Redux, just the view layer shouldn’t be able to access anything else except the model. Even now, it is an antipattern in my opinion to reach anything from the view which has a state and it’s not in the model. Jakarta MVC, Spring MVC, and Struts are close to this, JSF’s model is the JNDI itself, so it’s even easier to write way worse spaghetti code.