>>>>> No more for me. >>>> >>>> Introducing more code into Pharo that depends on more parts of Pharo >>>> (RPackage, Announcement, Pragma, Ring, RB, Shout, ...) doesn't make it >>>> easier to maintain and change Pharo. Or did I misunderstand something >>>> about cohesion and coupling? :-) >>> >>> With that philosophy, we can just declare Pharo as finished and do something >>> else. >>> My point of view is that I invent new abstractions *and than use them* on >>> and >>> for the system itself. >> >> I disagree; I would like a small and stable Pharo in which crazy ideas >> can be realized. For that I don't need fancy abstractions, but a >> minimal, simple and absolutely stable system in which I can load and >> do whatever I want. Maybe this is just me? > > Is the current system simple and minimal?
No, it is complex and it is getting bigger with every release. > Do you think the Pharo we have is good enough to have a future? No, there is a lot to be improved. I think the future of Pharo is what can be built on top, not what can be integrated and forced upon everybody. Lukas -- Lukas Renggli www.lukas-renggli.ch
