I'm trying to fix some Pharo VM issues (11330), but have awfully bad experience with Pharo2.0 tools. The autocompletion stuff is a joke, it moves the input cursor randomly and spoils my input. That's the first thing I disable. The pharo's PolyMorphDiffTool is good looking but awfully sloooow It clearly does not scale (10 minutes or so to diff Eliot's branch) so I reverted to the old diff tool. But of course, someone broke MCMethodDefinition>>summary (gratuitously?) and I had to revert this method to have class names displayed again. But worse than all, there are insane caches operating in MCVersion that drove me crazy. Here is the scenario: 1) I diff working copy against package.branchA-version.mcz 2) I cherry pick and install a few methods 3) I diff against package.branchA-version.mcz again to check if I missed smthing 4) Huh? it looks like my cherry pick have not been installed??? Yes they were installed, but the completePackageSnapshot has been cached in MCVersion!!! What a mistake! The working copy is going to evolve, caching a snapshot of it is a DUMB thing.It means that methods that I further change in the working copy will NEVER be taken into account next time I'll do a diff. So I had to change MCVersion>>changes ^ self completeSnapshot patchRelativeToBase: self loadCompletePackageSnapshot This is so broken that I have to report here. Note that I did not check if symptoms are still in Pharo 3.0, but the working copy scnapshot cache still is for sure! Guys, it makes me wonder, who is eating the dog food? Did anyone progress into developing VM in Pharo 3.0, because if I must eat it, I'd prefer the freshest ;) Or if I fix some more bug, I'd like my efforts to not apply to an obsolete version.