- Pharo-dev - lists.pharo.org

Re: ANN: Experimental flatpak pharo vm v10.3.9

by Martin Dias

Same: $ flatpak run org.pharo.Pharo Pharo.image --interactive [ERROR] 2026-07-03 09:42:36.000 loadPharoImage (src/client.c:218):Image file not found: No such file or directory [ERROR] 2026-07-03 09:42:36.000 runVMThread (src/client.c:239):Error opening image file: Pharo.image I'll ask you via Discord El vie, 3 jul 2026 a la(s) 1:15â¯a.m., Esteban Lorenzano (estebanlm(a)netc.eu) escribiÃ³: > did you try > > flatpak run org.pharo.Pharo YourImage.image --interactive > > ? > > > On 7/3/26 03:53, Martin Dias wrote: > > Hi Esteban, > > Looks great, thanks. > > However, I got an error :) After following the instructions to install the > flatpak, it looks installed successfully: > > $ flatpak run org.pharo.Pharo --version > Pharo v12.0.3-beta Compiler: 15.2.0 > Built from: v12.0.3-beta+0.2aa4b7c - Commit: 2aa4b7c - Date: 2026-06-03 > 15:53:56 +0200 > > Then I downloaded a Pharo image but get this error: > > $ curl https://get.pharo.org/140 | bash > $ flatpak run org.pharo.Pharo Pharo.image > [ERROR] 2026-07-02 21:45:48.000 loadPharoImage (src/client.c:218):Image > file not found: No such file or directory > [ERROR] 2026-07-02 21:45:48.000 runVMThread (src/client.c:239):Error > opening image file: Pharo.image > > I tried with variants such as full path and get the same: > $ flatpak run org.pharo.Pharo "/tmp/Pharo.image" > > $ uname -a > Linux x 6.1.0-49-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.174-1 > (2026-05-26) x86_64 GNU/Linux > > Any idea? > > Martin > > El mar, 2 jun 2026 a la(s) 6:16â¯a.m., Esteban Lorenzano via Pharo-dev ( > pharo-dev(a)lists.pharo.org) escribiÃ³: > >> Hello, >> >> As some of you may know, Iâve been working on a Flatpak for the Pharo VM. >> After some work, I think I finally have a version thatâs ready to be >> tested, so please give it a try! >> >> You can find it here: https://forge.smallworks.eu/pharo/pharo-vm-flatpak >> Just follow the installation instructions in the repo. >> >> A few notes: >> >> - >> >> This is still a regular Pharo VM, but the bundled dependencies are >> the ones used by Pharo 14. This matters especially for Iceberg, since it >> uses libgit2 1.9.4. >> - >> >> For FFI, I had to update UnifiedFFI in Pharo 14 so it can find >> libraries in the right places. Since Flatpak runs in a sandbox, host >> libraries, when needed, are exposed under /run/host/.... The Pharo >> run script already adapts LD_LIBRARY_PATH for this, but uFFI does not >> use it. >> - >> >> This is a full VM with quite a few dependencies, including the GNOME >> runtime, because it is also part of another project that needs them. You >> can snoop around the repo, or wait for my ESUG talk to hear more about >> that. ;) >> - >> >> I tested it on my own Arch system and on Ubuntu 24. That said, it may >> still need some tweaks on other systems, or even on different machines >> running those same systems, so please let me know how it goes. :) >> >> Cheers ! >> Esteban >> >

July 3, 2026

Re: ANN: Experimental flatpak pharo vm v10.3.9

by Esteban Lorenzano

did you try flatpak run org.pharo.Pharo YourImage.image --interactive ? On 7/3/26 03:53, Martin Dias wrote: > Hi Esteban, > > Looks great, thanks. > > However, I got an error :) After following the instructions to install > the flatpak, it looks installed successfully: > > $ flatpak run org.pharo.Pharo --version > Pharo v12.0.3-beta Compiler: 15.2.0 > Built from: v12.0.3-beta+0.2aa4b7c - Commit: 2aa4b7c - Date: > 2026-06-03 15:53:56 +0200 > > Then I downloaded a Pharo image but get this error: > > $ curl https://get.pharo.org/140 | bash > $ flatpak run org.pharo.Pharo Pharo.image > [ERROR] 2026-07-02 21:45:48.000 loadPharoImage > (src/client.c:218):Image file not found: No such file or directory > [ERROR] 2026-07-02 21:45:48.000 runVMThread (src/client.c:239):Error > opening image file: Pharo.image > > I tried with variants such as full path and get the same: > $ flatpak run org.pharo.Pharo "/tmp/Pharo.image" > > $ uname -a > Linux x 6.1.0-49-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.174-1 > (2026-05-26) x86_64 GNU/Linux > > Any idea? > > Martin > > El mar, 2 jun 2026 a la(s) 6:16â¯a.m., Esteban Lorenzano via Pharo-dev > (pharo-dev(a)lists.pharo.org) escribiÃ³: > > Hello, > > As some of you may know, Iâve been working on a Flatpak for the > Pharo VM. After some work, I think I finally have a version thatâs > ready to be tested, so please give it a try! > > You can find it here: > https://forge.smallworks.eu/pharo/pharo-vm-flatpak > Just follow the installation instructions in the repo. > > A few notes: > > * > > This is still a regular Pharo VM, but the bundled dependencies > are the ones used by Pharo 14. This matters especially for > Iceberg, since it uses libgit2 1.9.4. > > * > > For FFI, I had to update UnifiedFFI in Pharo 14 so it can find > libraries in the right places. Since Flatpak runs in a > sandbox, host libraries, when needed, are exposed under > |/run/host/...|. The Pharo run script already adapts > |LD_LIBRARY_PATH| for this, but uFFI does not use it. > > * > > This is a full VM with quite a few dependencies, including the > GNOME runtime, because it is also part of another project that > needs them. You can snoop around the repo, or wait for my ESUG > talk to hear more about that. ;) > > * > > I tested it on my own Arch system and on Ubuntu 24. That said, > it may still need some tweaks on other systems, or even on > different machines running those same systems, so please let > me know how it goes. :) > > Cheers ! > Esteban >

July 3, 2026

Re: ANN: Experimental flatpak pharo vm v10.3.9

by Martin Dias

Hi Esteban, Looks great, thanks. However, I got an error :) After following the instructions to install the flatpak, it looks installed successfully: $ flatpak run org.pharo.Pharo --version Pharo v12.0.3-beta Compiler: 15.2.0 Built from: v12.0.3-beta+0.2aa4b7c - Commit: 2aa4b7c - Date: 2026-06-03 15:53:56 +0200 Then I downloaded a Pharo image but get this error: $ curl https://get.pharo.org/140 | bash $ flatpak run org.pharo.Pharo Pharo.image [ERROR] 2026-07-02 21:45:48.000 loadPharoImage (src/client.c:218):Image file not found: No such file or directory [ERROR] 2026-07-02 21:45:48.000 runVMThread (src/client.c:239):Error opening image file: Pharo.image I tried with variants such as full path and get the same: $ flatpak run org.pharo.Pharo "/tmp/Pharo.image" $ uname -a Linux x 6.1.0-49-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.174-1 (2026-05-26) x86_64 GNU/Linux Any idea? Martin El mar, 2 jun 2026 a la(s) 6:16â¯a.m., Esteban Lorenzano via Pharo-dev ( pharo-dev(a)lists.pharo.org) escribiÃ³: > Hello, > > As some of you may know, Iâve been working on a Flatpak for the Pharo VM. > After some work, I think I finally have a version thatâs ready to be > tested, so please give it a try! > > You can find it here: https://forge.smallworks.eu/pharo/pharo-vm-flatpak > Just follow the installation instructions in the repo. > > A few notes: > > - > > This is still a regular Pharo VM, but the bundled dependencies are the > ones used by Pharo 14. This matters especially for Iceberg, since it uses > libgit2 1.9.4. > - > > For FFI, I had to update UnifiedFFI in Pharo 14 so it can find > libraries in the right places. Since Flatpak runs in a sandbox, host > libraries, when needed, are exposed under /run/host/.... The Pharo run > script already adapts LD_LIBRARY_PATH for this, but uFFI does not use > it. > - > > This is a full VM with quite a few dependencies, including the GNOME > runtime, because it is also part of another project that needs them. You > can snoop around the repo, or wait for my ESUG talk to hear more about > that. ;) > - > > I tested it on my own Arch system and on Ubuntu 24. That said, it may > still need some tweaks on other systems, or even on different machines > running those same systems, so please let me know how it goes. :) > > Cheers ! > Esteban >

July 3, 2026

Re: ANN: Experimental flatpak pharo vm v10.3.9

by sducasseatwork＠mailo.com

Hi esteban excellent news. Did you announce it on the pharo news web site? S > On 2 Jun 2026, at 12:15, Esteban Lorenzano via Pharo-dev <pharo-dev(a)lists.pharo.org> wrote: > > Hello, > > As some of you may know, Iâve been working on a Flatpak for the Pharo VM. After some work, I think I finally have a version thatâs ready to be tested, so please give it a try! > > You can find it here: https://forge.smallworks.eu/pharo/pharo-vm-flatpak > Just follow the installation instructions in the repo. > > A few notes: > > This is still a regular Pharo VM, but the bundled dependencies are the ones used by Pharo 14. This matters especially for Iceberg, since it uses libgit2 1.9.4. > > For FFI, I had to update UnifiedFFI in Pharo 14 so it can find libraries in the right places. Since Flatpak runs in a sandbox, host libraries, when needed, are exposed under /run/host/.... The Pharo run script already adapts LD_LIBRARY_PATH for this, but uFFI does not use it. > > This is a full VM with quite a few dependencies, including the GNOME runtime, because it is also part of another project that needs them. You can snoop around the repo, or wait for my ESUG talk to hear more about that. ;) > > I tested it on my own Arch system and on Ubuntu 24. That said, it may still need some tweaks on other systems, or even on different machines running those same systems, so please let me know how it goes. :) > > Cheers ! > Esteban >

July 2, 2026

Default development branch moved to Pharo15

by Esteban Lorenzano

Hello, I moved the pharo-project/pharo repository to Pharo15 branch. New features need to go there :) cheers ! Esteban

June 30, 2026

A note on the Pharo 14 release

by Esteban Lorenzano

Hello Pharo users and developers, You may have noticed that our usual AprilâMay release did not happen this yea. We wanted to explain why Pharo 14 has been delayed, and why we are still not quite at the point where we want to release it. There is not much mystery: we got very ambitious about what we wanted to include. We are still finishing a few important pieces that we believe need to be part of this release, as they will provide foundations for the next development cycle. Here is a non-exhaustive list of what we are aiming to include: * Massive changes in the VM (v12) * Migration to SDL3 as the backend * Alexandria, as a future replacement for Athens * A Bloc preview â yes! * Toplo, the new widget set based on Bloc, and a SpecâToplo preview * And many other things that are not polished enough yet So, yes, we are disappointed not to have met our usual release cycle. But we believe the extra time will be worth it â once we get there :) Cheers, Esteban

June 26, 2026

Re: An Inference engine inside Pharo for LLMs

by S Krish

Great work. Will try it out sometime ahead. My notes from few months back: """ Pharo can offer new possibilities . LLM : processing of intent into code sent to pharo agents. All of non deterministic/ deterministic logic that is transformed to code to operate on input data Pharo agents: live environment that compiles in fraction of seconds.. perhaps milliseconds. Runs instant unit tests. Distribute verified runtime patch to other agents .. rather than messy library for everything like java/ python scaffold everything from its memory Object datastore: zero impedance non relational exactly mapped object data store with all of ACID properties if needed """ On Fri, 26 Jun, 2026, 03:20 omar abedelkader, <omar.abedelkader(a)inria.fr> wrote: > Hello everyone, for the first time, we have the first prototype of an > inference engine without any connection to any of the external provider > like Ollama, LMStudio, or vLLM. > > [image: pharo-infer.png] > > pharo-llm/pharo-infer: pharo-infer is a inference engine inside Pharo > <https://github.com/pharo-llm/pharo-infer> > github.com <https://github.com/pharo-llm/pharo-infer> > <https://github.com/pharo-llm/pharo-infer> > > > > [image: Capture dâeÌcran 2026-06-25 aÌ 23.40.41.png] > â > OA > >

June 26, 2026

An Inference engine inside Pharo for LLMs

by omar abedelkader

Hello everyone, for the first time, we have the first prototype of an inference engine without any connection to any of the external provider like Ollama, LMStudio, or vLLM. https://github.com/pharo-llm/pharo-inferï¿¼ pharo-llm/pharo-infer: pharo-infer is a inference engine inside Pharo github.com ï¿¼ â OA

June 25, 2026

ANN: pharo bindings for QREncode

by Esteban Lorenzano

Hello, Looking for small examples for (one of) my ESUG talks, I generate bindings forÂ this small tool: https://fukuchi.org/en/works/qrencode/ You can have things like this: https://github.com/pharo-cig/pharo-libqrencode I think it can be pretty useful :) Cheers ! Esteban

June 22, 2026

Re: "Claude, My New Pair Programming Partner" â New blog post on all: objects all: theTime

by Aaron Wohl

No matter how bad you think AIs are, I think there are some areas they are always useful: - scaffolding -- I have seen large projects fail because the later phases couldn't start until it was too late. If you have a good spec for a big project and all the interface points, an AI is great for making temporary working implementations of all the parts. Although it can raise amuzing questions when a 6-month 2-person project has a 100% working scaffold in a weekend. - Code reviews with an LLM. An agent has a limited token space. But with a custom LLM looking things like code vs comment discrepancies, it can turn up a lot of issues. ----- Original message ----- From: Esteban Lorenzano via Pharo-dev <pharo-dev(a)lists.pharo.org> To: pharo-dev(a)lists.pharo.org Cc: Esteban Lorenzano <estebanlm(a)netc.eu> Subject: [Pharo-dev] Re: "Claude, My New Pair Programming Partner" â New blog post on all: objects all: theTime Date: Sunday, June 07, 2026 12:39 PM I like what Linus Torvalds say here : https://thenewstack.io/torvalds-ai-programming-productivity/ In the best of cases, is a productivity tool. Just like compilers were at a point (compilers did not have all the ecological issues associated, of course). The first thing we need to do is stop anthropomorphizing tools. It really freaks me out when people talk about LLMs â and agents â as if they were human. Esteban On 5/8/26 17:26, Stephane Ducasse via Pharo-dev wrote: > I love it. > IA look like crap generator. > > I see in some text Iâm reading. > So for the code I can image. > > S > > >> On 8 May 2026, at 10:17, Nicolas Anquetil <nicolas.anquetil(a)inria.fr> wrote: >> >> About AI and truck factor >> >> This post https://www.shapeandship.ai/p/cheap-to-build-costly-to-keep argues that with AI coding the truck factor tends toward 0... >> *In a post-mortem, this surfaces as "nobody knew this code existed," which is worse than "only one person knew."* >> >> They talk about "comprehension debt" (evolution of the technical debt concept) >> >> cheers >> >> nicolas >> >> On 2026-05-07 22:01, Koen De Hondt wrote: >>> Dear Pharo users and developers, >>> >>> I posted a first article in a series about using AI in Pharo development. After seeing the world embrace agentic development tools, I decided it was time to look into them and see how they can be used for software development in Pharo. >>> >>> https://all-objects-all-the-time.st/#/blog/posts/24 >>> >>> As always, all feedback is welcome. >>> >>> Happy reading! >>> >>> Ciao, >>> Koen >> -- >> Nicolas Anquetil >> Evref team -- Inria Lille

June 7, 2026