2013/12/24 kilon alios <kilon.al...@gmail.com> > I agree too , having realistic expectations is the wise thing to do. All > of us want the Stars and the Moon , the question is what we can really > have and that we all or at least most of us do contribute even in very > small portions. Whats better way to live than improve the very things we > love ? > > Personally I love all the new "unclean" things I see in pharo. Why keep > things in a closet because of unknown bugs, unleash them to the world and > let the world shape them to something mature. Thats how you make great > code. > > > On Tue, Dec 24, 2013 at 3:52 PM, Stéphane Ducasse < > stephane.duca...@inria.fr> wrote: > >> >> >> 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 >> > >
I understand, lack of time/manpower. But if we have the time, to introduce new or experimental things, we should focus to have stable tools.