I think the issue stems from not using Pharo by choice. Apparently he canât continue to use VW for political reasons, and is annoyed at having to port everything to an open source Smalltalk. Iâd probably be annoyed myself if I had to port something I did 15 or 20 years ago in VisualAge or IBM Smalltalk, whatever I had to port it to. Iâve only had to port one project from Pharo to an IBM Smalltalk server process, so that it could run on a 128 thread UltraSparc. If I were any use writing compilers I could have ported Pharo itself, unfortunately Iâm not. The options thatâve been given are workable. The advantages of Pharo are not going to be obvious if youâre only porting code written elsewhere, while differences are going to be right in your face. Andrew From: Stephane Ducasse Sent: Sunday, November 12, 2017 10:05 AM To: Any question about pharo is welcome Subject: Re: [Pharo-users] Pharo-users Digest, Vol 55, Issue 94 Joachim We are focused on deployment but not the same way. We are the first system that bootstrap a core and can load dependencies on this core. We have a dependency analyser that is really advanced since it can check that you have message that are not in extension of packages that you use. In January I hope that we will start packaging Applications (versus packaging code), so that people can deploy desktop applications more easily. Now if people like vikenti wants our support. They should learn how to engage a discussion with us and not just complain :) Stef On Sun, Nov 12, 2017 at 6:02 AM, jtuchel@objektfabrik.de <jtuchel@objektfabrik.de> wrote:
Am 11.11.17 um 22:29 schrieb ÐикенÑий ÐоÑапов:
Vikenti,
And also i mean some simple and understandable deployment tool (as in Cincom VW exists) but not manual-written bash scripts. This tool asks me what class\accessor send open message, asks what to strip and how to pack my image. Few simple steps and i have perfectly cleaned minimal image with all image started methods tuned to load necessary class. It's really cool stuff. It's a pity, my low-level SmallTalk knowledge (VW + Pharo) is not enough to port this tool or create the new one.
just out of curiosity and following my first reflex: if VisualWorks offers most of what you need and is essentially what you want - why do you want to switch to Pharo?
This is not intended to be offensive or provoking. I just wonder if an open source project is the right thing for you. Pharo is emerging and has quite some pace doing so. This is both good and bad - at many levels. Commercial offerings may be a lot slower and thus less of a "moving target" (not sure I am citing you, but I know I read this in one of the threads about the current state of Pharo just these days), but they are pretty much focussed on issues like deployment and stable APIs.
Joachim