With respect, please re-read your post, with emphasis on "A snapshot of an old Windows machine can run on a virtual machine forever, whereas keeping an operating system compatible forever is bound to fail." I do not agree that virtualization is fix-all goodness, and I have concerns about trying to have various versions of important classes in the image. Bill -----Original Message----- From: pharo-project-bounces@lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Marcus Denker Sent: Tuesday, January 26, 2010 5:10 PM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] Gardening/ScriptManager On Jan 26, 2010, at 10:59 PM, Schwab,Wilhelm K wrote:
Not so fast, all you have to do is sprinkle some .net dust on the computer and everything will be fixed until the next time MS changes their mind, right?
Sorry, couldn't resist. Ironically, I find that software written to MS specs breaks readily; things written with anything up through contempt for them seems to work just fine. I stop short of seeing a vm as allowing one to run Windows in perpetuity, but that is another debate.
This was not about Microsoft or Windows, nor about virtualization in particular. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD. _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project