2012/5/6 Guillermo Polito <[email protected]>: > > > On Sun, May 6, 2012 at 2:16 PM, Esteban Lorenzano <[email protected]> > wrote: >> >> <snip> >> I'm more worried about having all-platforms-specific-stuff inside image... >> but we can mitigate that with fuel, and making loadable packages when >> running the image... I don't know, I'm just thinking while writing, so, this >> is probably stupid :) >> > > Just think how many times you took a development image and used it in > several platforms. At least I don't. Same happened when I used Eclipse. I > didn't share my eclipses between systems. Even, I had several eclipse > installations with their own plugins (just like images, hehe). > > Probably with jenkins, metacello, and kernel/bootstrap we can generate > distributions per platform (With the possibility of an all-in-one > distribution for the ones who like that). > > Guille
Yes, I understand that we can live without this feature... - If we can reconstruct images easily (one of the goal of Pharo) - I mean not only code, but any object (eventually with Fuel) - If we solve the bootstrap problem (or if we can still prepare an image for cross platform startup) - If we don't forget to always talk (send messages) thru an abstract layer, and never directly name the target library, Since I didn't have all these tools in the past, I were forced to use development images across different platform a lot, and yes, it was not following the mainstream rules (a la "we can reconstruct all from scratch") but damn powerful. For deploying applications, it also is very powerful and cheap. Personally, I would feel sore to lose it. Nicolas
