+1 on thanks to INRIA and congratulations to Igor. One suggestion I'd like to add: while he is cleaning the VM code, it would be nice to work toward having a path for information on failures to reach the outside world in some way. Can't load a library? Where did you look for it? We can't anticipate everything somebody might want to know, but the status quo is to report nothing and we can do better, especially when the VM translates parameters from the image before using them.
On Linux, not every library is a plugin. IIRC, the blurring of that distinction is mostly in the minds of the community, but the occasional .so for number crunching, creating graphics or hardware interfacing needs a home too. ________________________________________ From: pharo-project-boun...@lists.gforge.inria.fr [pharo-project-boun...@lists.gforge.inria.fr] On Behalf Of Germán Arduino [gardu...@gmail.com] Sent: Saturday, December 11, 2010 10:08 AM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] good news of the year Yes, indeed very very good news! Congrats Igor, of course, but a big thanks to INRIA for invest in Smalltalk! 2010/12/11 Esteban Lorenzano <esteba...@gmail.com>: > He, I was about to say "congratulations to Igor", but I better say > "congratulations to all us, the pharoers, for having Igor as a full time > engineer" > > Cheers, > Esteban > > El 11/12/2010, a las 8:31a.m., Oscar Nierstrasz escribió: > >> >> +1 !!! >> >> On 11 Dec 2010, at 10:46, Stéphane Ducasse wrote: >> >>> Hi all >>> >>> We have a really good news for pharo. Igor got a job as engineer in our >>> team for two years. >>> We are really thankful to INRIA for that. Since we want to be transparent >>> here is the way we plan to work. >>> We asked igor to help fixing bug fixes for about 20% of his time. >>> And to focus on larger items. Here is a list based on the brainstorming we >>> did and what we told INRIA >>> igor would do. >>> Now if you want to help and join effort with us this is even better. >>> >>> Now igor started to work on OPAL because we would like to have it for a >>> beta in january, when we will get a new unstable >>> stream. >>> >>> Stef >>> >>> -- Set nil >>> -- Hashed Collection >>> -- dictionary are slower >>> -- Generalize stream protocol #readInto:startingAt:count: >>> >>> -- WeakStructure >>> -- Finalizer >>> -- Chapter on Finalizer >>> >>> -- Better integration process >>> >>> -- EventSensor >>> polling >>> - publish a windows VM that support it >>> >>> -- ClassBuilder rewrite >>> >>> -- Helping improving the VM >>> - cleaner code >>> >>> -- Cleaning events/annoucement >>> check CUIS >>> on:send: >>> changed:/update >>> >>> -- SystemChangeNotification -> announcement >>> sync with Cyrille >>> review with Cyrille >>> >>> -- Using RPackage in Monticello >>> sync with cyrille >>> >>> -- iSqueak New event hierarchy >>> Alain imported that >>> Multitouch? >>> >>> -- New compiler >>> -- debug >>> -- Decompiler IR -> AST >>> -- Cleanups >>> -- API >>> -- Environment >>> >>> -- ROME API >>> - API stablisation: openVG >>> - system rewrite to use API >>> >>> -- Ephemerons ?? >>> >>> -- Announcement with weak structure >>> >>> -- Networks >>> - may be use WeakFinalizer here. >>> - looking at Andreas fixes in Squeak >>> >>> >>> >> >> > > >
