On 06 Feb 2014, at 19:51, kilon alios <kilon.al...@gmail.com> wrote:
> thats very good news , 64 bit is rather close now which mean even more C > libraries available for Pharo and loads of GB of memory to exploit. yes, but just *closer*… we'll still need the 64bits FFI :) > > > On Thu, Feb 6, 2014 at 7:19 PM, <b...@openinworld.com> wrote: > Clément Bera wrote: >> >> Hello pharoers, >> >> The new Cog memory manager, Spur, is simply *amazing*. I saw at FOSDEM that >> some of you were interested in it, but unfortunately you were lacking >> information about it. >> >> I wrote a one page article that sums up Spur's new features so every one can >> know what will be better. There's no VM technical details here, it's just >> about what will change for a regular pharo user. >> >> http://clementbera.wordpress.com/2014/02/06/7-points-summary-of-the-spur-memory-manager/ >> >> Let me know if you think I forgot yet another feature. >> >> If you have questions, I'll try to answer, but ask Eliot, he implemented >> Spur so he can answer your questions much better than I can :-). >> >> Regards, >> >> Clément > > In what way would the speed-up for Characters being immediate improve Unicode > performance, and/or would it be worthwhile having an immediate representation > of UnicodeCharacters? I found Roassal to go an order of magnitude slower when > displaying labels with Unicode (but there may be many reasons for that) ? > > cheers -ben >
