I’m thinking every Smalltalk would have an Iceberg. It would be the go-to tool for versioning and conversion of Smalltalk code for any environ.
Let it makes this clear. I’m personally not interested in moving code from Pharo to VW. I gave its chance long time ago to VW and I only got bad feelings and frustration. Yes, the bad feelings mostly pass; it takes many years. But there are still those occasional, special moments of deep resentment. So do not expect me to push any action in this direction. The same applies to Squeak. If I would not have created Pharo I would work in Ruby or Python. People paid by VW should do their job not me. Or you can do it if this is in your roadmap. My goal is to have the best environment possible and I’m working to make it. My goal is not to have a smalltalk system compatible with the rest of the universe. Now since people deploy on Gemstone we will pay attention to them and ideally I would love to have the ressources to make Pharo fully execute with compiler and other on top of GS VM. Now GS is not VW. :) Yes, GS is a very different system. For now, I’ll settle for getting Iceberg to work reliably in 7.0.3. Perfect. We all use it daily so let know. Are the best references on Iceberg the Pharo books or the Iceberg GitHub site? Check both you may find some little differences but in general this is stable. Which Iceberg material is most up-to-date for Pharo 7.0.3? I do not know. Nothing important changes between 7.0.3 and 8. Is anyone reporting stability/VM problems with Pharo installed to a non-default directory and/or when working with GitHub repos not kept in the default subfolder of the image folder? I do not know. Windows is often a pain (with file name encodings and others). Indeed, Windows is a pain. If you report situations that we can reproduce and that are not super super specific we will definitively have a look. My Pharo 3.0.7 install and all repos are in non-default directories, and I’m wondering whether this is causing the crashes. I do not know what is a non-default repo. I’m referring only to a non-default directory for the repo files, which you would think would not matter, or perhaps a file-not-found exception would be raised. But I don’t see that. On Windows, the default folder is in an \images subfolder. I currently keep all my Git repos on a separate RAID drive. Now on windows the state of the libraries to run scripts is making us trouble Can you give more details on that? What are the problems? and we will have to fix it. Shaping
