On 30 August 2011 02:58, Douglas Brebner <[email protected]> wrote: > On 29/08/2011 21:41, Stéphane Ducasse wrote: >> >> So may be you do not like Ring and this is ok. >> Now I want an abstraction so that we can build a remote browser by >> plugging simply rTalk + nautilus + ring. >> With the current state of the system this was simply impossible. >> >> I want to be able to browse senders in the past and compare them with the >> current version. Because we use >> prehistorical tools even if we could have something like torch to help us. >> >> I cannot see anymore SystemChangeNotifier (even if this was far better >> than without) >> PackageInfo, PackageOrganizer with lazy identification of packages >> so that when you do an analysis you have to ask sometimes twice to >> packageOrganiser and packageInfo. Ask cyrille the time he spent there. >> >> I want one good browser, one code model (to be used by all the tools), one >> system notifier and a good one. >> One AST. >> > > If I may make a metaphor, it sounds like rebuilding a house from the > foundations on up while you're living in it. Things are bound to get > unpleasant while it's happening, but it's still worth it in the end. :) >
Yes.. I agree with Stef. Compatibility (including backward's one) is good to have when it worth it. But keeping compatibility with crap (okay, okay lets call it poorly designed software)? Why? Of course we can focus our energy somewhere else.. But then i think it will be not making Pharo, but more making things on top of it. Still there's a lot to do in Pharo. Maybe for Lukas it is unclear.. i'm not sure. But we are agree in one thing: we want to fix stuff even if its not broken , because the way it works is against laws of logic, software engineering, common sense etc.. And i can remind everyone: nobody forcing people to use latest stuff. I know that commercial applications are at least 1 year behind the current version. That's the way it works and not only for Pharo, but for most other software in the world. And there is nothing bad with it. Personally, if i would be involved in commercial project, i would just pick one version of image and stick with it to the death. Because often there's much more to care about inside a project itself (development, support etc), and you usually having deadlines.. so trying to cope up with latest and greates stuff at the same rate as it appears would be just silly and waste of energy. -- Best regards, Igor Stasenko AKA sig.
