Interesting concept (one that i actually stumbled upon a couple of years ago).
If i would venture to guess why people don't use it more often i would say that it's because the marginal win (ease of debugging for a certain class of hard bugs) is smaller then the hassle of changing the complete toolset (current debugger and tools).
My guess this kind of tool is really good at a small class of hard bugs (which in general are pretty rare). For all the other the current tools are good enough so a switch would be costly for no immediate gain.
Eclipse will automatically update the running classes with the latest code that compiled. If you aren't changing method or class signatures then it will work like that :)
I want to do the same (not suck at it) so i started to look at web design communities a while ago. I found some interesting things that helped me be a little better:
If i would venture to guess why people don't use it more often i would say that it's because the marginal win (ease of debugging for a certain class of hard bugs) is smaller then the hassle of changing the complete toolset (current debugger and tools).
My guess this kind of tool is really good at a small class of hard bugs (which in general are pretty rare). For all the other the current tools are good enough so a switch would be costly for no immediate gain.