June 22, 2010
9:16 p.m.
We will see :) let us make 1.2 another cool version. For now let us release 1.1 each step at the time.... Stef On Jun 22, 2010, at 8:17 PM, Yanni Chiu wrote: > Schwab,Wilhelm K wrote: >> I am very excited about Cog, but also have to urge some caution: There was mention of Seaside not running on it, which is a show-stopper until fixed. > > Yes, that's what I meant by fix major bugs. But given the level of excitement and interest, I figured these would be fixed, long before a Pharo 1.2 would be released. > >>> Henrik Johansen wrote: >> - Platform availability (64bit is not supported, iPhone/iPad VM's can't run them) >> - Still buggy (I've reported 2 so far) >> - No process established yet how / if to synch with current VMMaker (which contains quite a lot of fixes not found in Cog) >> - Plugin availability (f.ex. I tried building FT2Plugin using Cog structure on OSX, and failed miserably) >> - No good reason to release a backwards-incompatible image by default, when Cog translates them by default, but not the other way around. > > Yes, these are all very good points. The last point is the best, there's no reason not to, since Cog can translate it. > > I just have a feeling that dragging out a transition like this would be more painful than a quick leap. I know that for me, as soon as Seaside runs on MacOSX and Linux, I'd make the move. I'd probably hold back if it was only 1.5 times speed-up, but likely 3 times or more, is hard to resist. It's not easy to always know which VM you're running, so there's almost certainly going to be image mis-matches, the longer the transition takes. > > Now that I think about it, for me, I can simply change the two VM's I use. It's just the image builders that need to pick up the right VM (if they happen to use Cog day-to-day), and keep everything straight. > > > _______________________________________________ > Pharo-project mailing list > Pharo-project@lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project