> I really do not understand where this feeling of bloating comes from. Perhaps > it is from the fact that for a transitional period, we will have a couple of > systems in parallel. But, this is necessary to move things forward and to > have a smooth transition: > - The Announcements will replace SystemNotifier which is a hack > - The RPackage will replace PackageInfo which is a hack > - To remove PackageInfo and friends, we need to get the tools to work with > RPackage > - I did not have enough time to take a closer look at Ring, but from what I > understood it does not add much code but it should provide a nice layer for > unifying several abstractions that were used for tools > - The old browser is a hack, so Nautilus should be a minimal implementation > of a new browser that works with the RPackage. Now, I am not sure if Nautilus > did manage to be minimal, but it would be a good goal and in the end it will > result in a reduced code base. > - Shout can probably be debated, but for the little code that is added, it is > not > - RB should be in the image because it is essential for people that want to > code (and the developers that maintain the image do want that) > > I find these to be the right decisions. Having Core + Dev did not make sense > because people that maintain Core, did not have the tools. Unifying the two > with minimal overhead (and it is minimal in my view) is the right way to go. > > Besides, stressing the creation of a PharoMini will make sure things are > modular.
Thanks This is why we were working on a bootstrap, not just for fun. And yes our goal is to have a nice layered system with decent abstraction and not spaghetti code. For me stable means that we can build something without having to reimplement everything because everything is so brittle that each time we change something simple all the system shake. Stef
