yes! Maybe a solid core with a layer of fast evolving things.
That's the model for Hortonworks now. A stable Hadoop core for stability and fast updates for things like Spark. Phil On Mar 25, 2016 6:19 PM, "Hilaire" <[email protected]> wrote: > Not exactly related to Announcement, but I remember when I first port > DrGeo to Squeak (at that time Pharo did not exist) I used a lot of > change/update when objects in the canvas changed. It was terribly slow, > and later opted for a top-down update in the list of object. > > So some sometime what look like a cool stuff (decoupled objects) is just > a drag. > > Regarding optimizing, I share my opinion here months ago, I think Pharo > need consolidation releases: no new features, only bugs fix and speed > improvement. There are enough new features in Pharo for a couple of > years, but the product need to *be* solid and *feel* solid. > > Hilaire > > Le 25/03/2016 12:33, Stephan Eggermont a écrit : > > On 25-03-16 11:49, Nicolai Hess wrote: > >> Morphic drasticallly slower ? I would expect morphic code is mostly > >> the same in pharo and squeak. If pharo is slower, this is a good > >> starting point for optimising. Can you gives some hints? > > I do not have the impression that morphic is so much slower. > > We had/have a problem of too many announcements being send and > > too many redraws happening. > > > > Stephan > > > > > > -- > Dr. Geo > http://drgeo.eu > > >
