October 2019 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Import a pharo 6 image in pharo 7

by Sean P. DeNigris

Sven Van Caekenberghe-2 wrote > You could try to serialise/deserialise your data with... FUEL (binary). If you use Fuel, this may help: https://github.com/seandenigris/pharo/wiki/Cookbook#fuel-migration ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Oct. 18, 2019

Re: [Pharo-users] Smallest docker image for pharo >=7 ?

by Tim Mackinnon

This is a better link: https://workingcopy.app/git/#path=scripts/build.sh&repo=git@gitlab.com:mact… Sent from my iPhone > On 18 Oct 2019, at 16:18, Tim Mackinnon <tim(a)testit.works> wrote: > > Hi Norbert - itâs all in the gitlab repo (the idea was to fork it and configure your own pipeline e vars) > > However the key stuff was in the scripts dir, and this file - /scripts/build.sh > > Which also loads some .st files for image fix ups . > > Tim > > Sent from my iPhone > > > > Sent from my iPhone >> On 18 Oct 2019, at 16:07, Jan van de Sandt <jvdsandt(a)gijjes.nl> wrote: >> >> Hi Norbert, >> >> Last year I did some experiments with Pharo Lambda functions, see: >> >> https://github.com/jvdsandt/pharo-aws-toolbox/blob/master/doc/pharo-lambda-… >> >> I didn't spend a lot of time on minimizing the image. There is still a lot of room for improvement. >> >> Jan. >> >> >> >> >>> On Fri, Oct 18, 2019 at 12:30 PM Norbert Hartl <norbert(a)hartl.name> wrote: >>> Tim, >>> >>> is there a document anywhere explaining how to do a lambda image? >>> >>> Norbert >>> >>> > Am 18.10.2019 um 11:00 schrieb Tim Mackinnon <tim(a)testit.works>: >>> > >>> > ï»¿I havenât tried in a while, but in 2017 with PharoLambda I had a combined Pharo image and VM size if 21 mb using the early Pharo minimal (I recall it was an early 7.0 image ). I was loading a simple hello Alexa app, so not a ton of code (but it had Neo Json and other AWS libs as a dependency I recall). >>> > >>> > Iâm interested in trying these Docker experiments, so Iâll have to look at some point and see if I can get similar sizes. >>> > >>> > As I scripted my build, I have the steps laid out. I recall there were many vm plugins not needed for a server install (sound etc) and I also ran a cleanup step in the image as there was lots of metacello stuff cached ... so Iâm sure tinier is possible even without candle. >>> > >>> > Tim >>> > >>> > Sent from my iPhone >>> > >>> >>> On 18 Oct 2019, at 07:48, Norbert Hartl <norbert(a)hartl.name> wrote: >>> >>> >>> >>> >>> >>> >>> >>>> Am 17.10.2019 um 02:00 schrieb JuliÃ¡n Maestri <serpi90(a)gmail.com>: >>> >>> >>> >>> As a side note, the final image size is not what really matters, if you have 20 different images all starting from the same base image (eg ubuntu:18.04) the base layer is shared among all images so the network / disk usage is less than the total size of the image. >>> >> >>> >> The overlayfs does only help here with the disk storage that is not multiplied. As the image is a memory dump of an individual image nothing can be shared there. So if you have 20 images you have 20 times the heap. So a small image is actually important. The vm is different. It is the same static file which will be paged into shared memory and the vm binary should be shared for all 20 runtimes. But the interpreter memory will not be shared so a small vm pays out as well. >>> >> >>> >> Norbert >>> >> >>> > >>> > >>> >>> >> >> >> -- >> Jan van de Sandt >> gsm: +31 (0)6 3039 5998

Oct. 18, 2019

Re: [Pharo-users] Smallest docker image for pharo >=7 ?

by Tim Mackinnon

Hi Norbert - itâs all in the gitlab repo (the idea was to fork it and configure your own pipeline e vars) However the key stuff was in the scripts dir, and this file - /scripts/build.sh Which also loads some .st files for image fix ups . Tim Sent from my iPhone Sent from my iPhone > On 18 Oct 2019, at 16:07, Jan van de Sandt <jvdsandt(a)gijjes.nl> wrote: > > Hi Norbert, > > Last year I did some experiments with Pharo Lambda functions, see: > > https://github.com/jvdsandt/pharo-aws-toolbox/blob/master/doc/pharo-lambda-… > > I didn't spend a lot of time on minimizing the image. There is still a lot of room for improvement. > > Jan. > > > > >> On Fri, Oct 18, 2019 at 12:30 PM Norbert Hartl <norbert(a)hartl.name> wrote: >> Tim, >> >> is there a document anywhere explaining how to do a lambda image? >> >> Norbert >> >> > Am 18.10.2019 um 11:00 schrieb Tim Mackinnon <tim(a)testit.works>: >> > >> > ï»¿I havenât tried in a while, but in 2017 with PharoLambda I had a combined Pharo image and VM size if 21 mb using the early Pharo minimal (I recall it was an early 7.0 image ). I was loading a simple hello Alexa app, so not a ton of code (but it had Neo Json and other AWS libs as a dependency I recall). >> > >> > Iâm interested in trying these Docker experiments, so Iâll have to look at some point and see if I can get similar sizes. >> > >> > As I scripted my build, I have the steps laid out. I recall there were many vm plugins not needed for a server install (sound etc) and I also ran a cleanup step in the image as there was lots of metacello stuff cached ... so Iâm sure tinier is possible even without candle. >> > >> > Tim >> > >> > Sent from my iPhone >> > >> >>> On 18 Oct 2019, at 07:48, Norbert Hartl <norbert(a)hartl.name> wrote: >> >>> >> >>> >> >>> >> >>>> Am 17.10.2019 um 02:00 schrieb JuliÃ¡n Maestri <serpi90(a)gmail.com>: >> >>> >> >>> As a side note, the final image size is not what really matters, if you have 20 different images all starting from the same base image (eg ubuntu:18.04) the base layer is shared among all images so the network / disk usage is less than the total size of the image. >> >> >> >> The overlayfs does only help here with the disk storage that is not multiplied. As the image is a memory dump of an individual image nothing can be shared there. So if you have 20 images you have 20 times the heap. So a small image is actually important. The vm is different. It is the same static file which will be paged into shared memory and the vm binary should be shared for all 20 runtimes. But the interpreter memory will not be shared so a small vm pays out as well. >> >> >> >> Norbert >> >> >> > >> > > > > -- > Jan van de Sandt > gsm: +31 (0)6 3039 5998

Oct. 18, 2019

Re: [Pharo-users] Smallest docker image for pharo >=7 ?

by Jan van de Sandt

Hi Norbert, Last year I did some experiments with Pharo Lambda functions, see: https://github.com/jvdsandt/pharo-aws-toolbox/blob/master/doc/pharo-lambda-… I didn't spend a lot of time on minimizing the image. There is still a lot of room for improvement. Jan. On Fri, Oct 18, 2019 at 12:30 PM Norbert Hartl <norbert(a)hartl.name> wrote: > Tim, > > is there a document anywhere explaining how to do a lambda image? > > Norbert > > > Am 18.10.2019 um 11:00 schrieb Tim Mackinnon <tim(a)testit.works>: > > > > ï»¿I havenât tried in a while, but in 2017 with PharoLambda I had a > combined Pharo image and VM size if 21 mb using the early Pharo minimal (I > recall it was an early 7.0 image ). I was loading a simple hello Alexa app, > so not a ton of code (but it had Neo Json and other AWS libs as a > dependency I recall). > > > > Iâm interested in trying these Docker experiments, so Iâll have to look > at some point and see if I can get similar sizes. > > > > As I scripted my build, I have the steps laid out. I recall there were > many vm plugins not needed for a server install (sound etc) and I also ran > a cleanup step in the image as there was lots of metacello stuff cached ... > so Iâm sure tinier is possible even without candle. > > > > Tim > > > > Sent from my iPhone > > > >>> On 18 Oct 2019, at 07:48, Norbert Hartl <norbert(a)hartl.name> wrote: > >>> > >>> > >>> > >>>> Am 17.10.2019 um 02:00 schrieb JuliÃ¡n Maestri <serpi90(a)gmail.com>: > >>> > >>> As a side note, the final image size is not what really matters, if > you have 20 different images all starting from the same base image (eg > ubuntu:18.04) the base layer is shared among all images so the network / > disk usage is less than the total size of the image. > >> > >> The overlayfs does only help here with the disk storage that is not > multiplied. As the image is a memory dump of an individual image nothing > can be shared there. So if you have 20 images you have 20 times the heap. > So a small image is actually important. The vm is different. It is the same > static file which will be paged into shared memory and the vm binary should > be shared for all 20 runtimes. But the interpreter memory will not be > shared so a small vm pays out as well. > >> > >> Norbert > >> > > > > > > > -- Jan van de Sandt gsm: +31 (0)6 3039 5998

Oct. 18, 2019

VW -> Pharo

by eftomi

Hi, What is currently the most efficient way to import a parcel / code from VW 8.3 to Pharo 7 or 8? Thanks and best wishes, Tomaz -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Oct. 18, 2019

[ANN] Next Pharo Sprint: Oct 25

by Marcus Denker

We will organize a Pharo sprint / Moose dojo Oct 25, starting at 10:00am. (Local Time Paris). Goals of this sprint: - Pharo 8: Fix issues from tracker https://github.com/pharo-project/pharo/issues <https://github.com/pharo-project/pharo/issues> Remote Sprint: Remotely, you can join us on Discord. During the sprint, we synchronize local and remote Pharo sprinters: http://pharo.org/contribute-events <http://pharo.org/contribute-events> We have added a Board to coordinate the work: https://github.com/orgs/pharo-project/projects/9 <https://github.com/orgs/pharo-project/projects/9> Known Local Sprint meetings - Lille/France: It will be at the Inria Lille, Building B, third floor (RMoD offices). As the building is not open to the public, please contact us before if you plan to come A list of all Pharo Event of the year an be found here: https://association.pharo.org/events <https://association.pharo.org/events>

Oct. 18, 2019

Re: [Pharo-users] String concatenation vs. Stream

by Kasper Ãsterbye

When would you consider it pointless to use streams and just concatenate away? Or even trying to profile the difference. For me, 3 or less. Sounds about right. Or if it fits within a line. Or if it makes the code significantly easier to read. Best, Kasper

Oct. 18, 2019

Re: [Pharo-users] String concatenation vs. Stream

by Kasper Ãsterbye

On 18 October 2019 at 08.00.13, Richard O'Keefe (raoknz(a)gmail.com) wrote: When is it pointless to introduce a WriteStream and just use #, ? When #, would not be in a loop or recursion. Constructing error messages, class initialisation code, that sort of thing. If you find yourself doing a lot of concatenations, you are probably missing an abstraction. For example, building up XML by string concatenation would be very silly: you want to build a tree and have it write itself to a stream. Absolutely agree. Streams use logarithmic extension of buffer, concatenation linear, but it is still amazing to see. I am working on a pillar to `Text` generator. Here I found concatenation to be simpler to handle as I can add bold, italics, indentation, etc. in a much simpler way. To use a streaming method I would have to introduce both Canvas and Aggregate brushes. Doable indeed, but much less concise. Best, Kasper

Oct. 18, 2019

Re: [Pharo-users] Smallest docker image for pharo >=7 ?

by Norbert Hartl

Tim, is there a document anywhere explaining how to do a lambda image? Norbert > Am 18.10.2019 um 11:00 schrieb Tim Mackinnon <tim(a)testit.works>: > > ï»¿I havenât tried in a while, but in 2017 with PharoLambda I had a combined Pharo image and VM size if 21 mb using the early Pharo minimal (I recall it was an early 7.0 image ). I was loading a simple hello Alexa app, so not a ton of code (but it had Neo Json and other AWS libs as a dependency I recall). > > Iâm interested in trying these Docker experiments, so Iâll have to look at some point and see if I can get similar sizes. > > As I scripted my build, I have the steps laid out. I recall there were many vm plugins not needed for a server install (sound etc) and I also ran a cleanup step in the image as there was lots of metacello stuff cached ... so Iâm sure tinier is possible even without candle. > > Tim > > Sent from my iPhone > >>> On 18 Oct 2019, at 07:48, Norbert Hartl <norbert(a)hartl.name> wrote: >>> >>> >>> >>>> Am 17.10.2019 um 02:00 schrieb JuliÃ¡n Maestri <serpi90(a)gmail.com>: >>> >>> As a side note, the final image size is not what really matters, if you have 20 different images all starting from the same base image (eg ubuntu:18.04) the base layer is shared among all images so the network / disk usage is less than the total size of the image. >> >> The overlayfs does only help here with the disk storage that is not multiplied. As the image is a memory dump of an individual image nothing can be shared there. So if you have 20 images you have 20 times the heap. So a small image is actually important. The vm is different. It is the same static file which will be paged into shared memory and the vm binary should be shared for all 20 runtimes. But the interpreter memory will not be shared so a small vm pays out as well. >> >> Norbert >> > >

Oct. 18, 2019

Re: [Pharo-users] String concatenation vs. Stream

by Sven Van Caekenberghe

> On 18 Oct 2019, at 07:59, Richard O'Keefe <raoknz(a)gmail.com> wrote: > > When is it pointless to introduce a WriteStream and just use #, ? > When #, would not be in a loop or recursion. > Constructing error messages, class initialisation code, that sort of thing. > > If you find yourself doing a lot of concatenations, you are probably > missing an abstraction. For example, building up XML by string > concatenation would be very silly: you want to build a tree and have > it write itself to a stream. +100

Oct. 18, 2019