>> I really like Nautilus, the groups, the history navigation, the code panel >> with the color warning for >> long methods. It is good doing experiments with new or better developer >> tools. >> >> But some parts just looking as "quickly hacked into it", just to make it >> running. >> And there are bugs. >> Nautilus could need some refactoring/code cleanup. >> >> In my point of view, in a clean and stable pharo release, >> all smalltalks tools (browser debugger inspectro ...) should show you >> "look, thats the way of doing it in smalltalk /pharo". >> >> >> I would really like to more emphasis on "clean and stable”.
Oh yes. Now if somebody has 5 engineers that do not know what to do, I have some ideas :) > Yes.. the problem is not the “want” but the “do”… in the end we always need > to manage > it with the limited resources we have… + 1 This is why we should simplify and clean it. Stef
