I still have production code (GemTools) that runs today in Pharo 1.1 ...
I assume that others also have production code running in older versions of Pharo and Squeak and GemStone so I make sure that Metacello continues to work on those platforms ...
Not everyone has the luxury of having the time to port their entire production catalog to the latest version of Pharo ...
I don't demand that zeroconf support Pharo1.2 as long as there is a way that I can keep downloading Pharo1.2 ... but if you don't intend to support all releases of Pharo on zeroconf, then I will simply start using the alternate long term method in my scripts because I certainly don't want to have to change scripts that are working perfectly fine, because you've decided to drop support for a particular version....
Dale On 3/22/15 11:46 PM, Marcus Denker wrote:
On 22 Mar 2015, at 22:56, Dale Henrichs <[email protected]> wrote: Damien, I'm using zeroconf for Pharo 1.2, 1.4 and 2.0 ... I still test Metacello against Pharo1.1 ... I would use zeroconf with 1.3 but there is something funkily different between what is available on zeroconf for 1.3 and what actually "works" for for 1.3 (https://gforge.inria.fr/frs/download.php/30567/PharoCore-1.3-13328.zip).I do not think that this is a good idea: we are not building a Museum. For example, we improve the core libraries. It will make something like Metacello *very* complex to be compatible over so many versions back. In the end, people who have this philosophy start to even request “to make this easier”, and then tell us to stop changing. Make your live easier and do *not* support old versions! Everything gets easier and the world will be a happier place. Marcus
