There is a good reason for that, the new debugger has got inspectors only since yesterday, so it was hardly usable before. Today I peer programmed all day long with Camillo on the new inspectors, based on Spec and a new model, and we are about to have something stable and nice. In a few days we will integrate it and then there will be still some details to clean with the new spec debugger (in the old inspector, inspect: used primitiveChangeClassTo: for the debugger, we want to avoid it for example). At this point, which will be before the end of this Pharo 3.0 iteration (so within a month), we may add an option to open�directly�full debugger with the new debugger.

� � � �"Is it desirable ?"

The new debugger is much better in term of design and internal implementation. It means for example that anyone can look at it and understand the code, or create its own debugger subclass for its project. It is also easy to maintain and remove a dependency to CodeHolder (the old debugger depends on it). But basically in term of user interaction, it is the same as the old one, except that it now lacks of some features, like inspectors or the context menu in the stack list. On the other hand, one day, when we will add the object centric debugging tool, we will be able to do it with this new debugger, whereas it would have been very hard with the old one. And this is a nice feature for day to day development and end users.