Given the fact that I am using a ton of time series at the moment, I feel that I'll be caught in this as well (Pharo for dev & prod).
What about having a look at this through a Google Hangout? Phil On Thu, Mar 27, 2014 at 11:17 AM, Johan Brichau <[email protected]> wrote: > Hi, > > This is indeed something we noticed moving to Pharo3: all our benchmarks > fail because of DateAndTime being slower. > Since we use Pharo only for development, it's not a showstopper for us, > but definitely an issue we are interested to help solving too. > > Johan > > On 26 Mar 2014, at 22:53, Stephan Eggermont <[email protected]> wrote: > > > DateAndTime is a very good candidate for some slot-tricks, > > and should probably be a value object. > > > > Stephan > > > > > > >
