- Pharo-dev - lists.pharo.org

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

by Cyril FERLICOT-DELBECQUE

-- Cyril Ferlicot-Delbecquehttps://ferlicot.fr On Sunday, June 7th, 2026 at 6:39 PM, Esteban Lorenzano via Pharo-dev <pharo-dev(a)lists.pharo.org> wrote: > 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. +1000 I find that really creepy and so many people are doing that. > 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>](mailto:nicolas.anquetil@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

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

by Esteban Lorenzano

in fact Linus says AI may increment productivity x10, but compilers did it x1000, so we are not quite close :) Esteban On 6/7/26 18:47, Nicolas Anquetil wrote: > > may be AI will allow us to raise the level of abstraction, just as > compilers, or OO did ? > > We (humans) will still program (through AI) but the programming > language will be different > > nicolas > > On 2026-06-07 18:39, Esteban Lorenzano via Pharo-dev wrote: >> >> 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 >>> > -- > Nicolas Anquetil > Evref team -- Inria Lille

June 7, 2026

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

by Nicolas Anquetil

may be AI will allow us to raise the level of abstraction, just as compilers, or OO did ? We (humans) will still program (through AI) but the programming language will be different nicolas On 2026-06-07 18:39, Esteban Lorenzano via Pharo-dev wrote: > > 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 >> -- Nicolas Anquetil Evref team -- Inria Lille

June 7, 2026

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

by Esteban Lorenzano

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

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

by sducasseatwork＠mailo.com

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

"Logging Interactions with the Iris MCP Server" â New blog post on all: objects all: theTime

by Koen De Hondt

Dear Pharo users and developers, I posted the fourth article in a series about using AI in Pharo development. After building the MCP server and pair programming with Claude to write code in a Pharo image, I decided to add logging to the MCP server to keep an eye on what Claude is doing. https://all-objects-all-the-time.st/#/blog/posts/27 As always, all feedback is welcome. Happy reading! Ciao, Koen

June 3, 2026

Pre-Pre-Announce: High Performance Parallel Smalltalk Achieved, Seek Donating Subscribers

by John B Thiel

= Pre-Pre-Announce: High Performance Parallel Smalltalk Achieved, Seek Donating Subscribers John B. Thiel 2026-june Contents: ABSTRACT OVERVIEW SEEK DONATING SUBSCRIBERS FOOTNOTE: SPECIAL NOTE TO PROFESSORS / ACADEMICS DISCLAIMER COPYRIGHT == ABSTRACT A High Performance Multi-Core Parallel Smalltalk System is under development and operational. I am seeking donating subscribers to begin support now, to reward my work to date and encourage bringing the system into existence and availability. Subscribers *may* be eligible for early access and news (no guarantees). == OVERVIEW The system expresses a multi-year design effort, has succeeded operational bringup, and feature buildout is proceeding. It has baseline performance comparable to Squeak/Cog, plus near linear Nx speedups across N cores for suitable algorithms. It is a well-grounded design, with reference to standards and theoretical foundations, and selection of high quality substrates. The system has been designed from day 1 for threadsafe, high performance parallelism including such iconic capabilities as efficient Threadsafe #Become, and is true multi-core -- a single process can use all cores. It is an entirely new design and re-imagining of a Smalltalk system. Not VM/Bytecode-based, nor an engine for any existing system. The system transpiles to an intermediate language/substrate, which is itself a powerful dynamic language, and thence to Native Machine Code. It is not Image-based in the classical sense of "snapshot the world". Objects must be manually persisted, and code is maintained in external files. I consider this a preferable model, to leverage the wide array of tools, editors, VCS, etc. The system does have a live running image, and classes, methods and objects can be dynamically loaded, defined and re-defined on-the-fly. As a fundamental design feature, there is a comprehensive portable external object format, capable to store/load most objects and arbitrary complex *graphs of objects*. The overall vision is a SYNTHESIS of two platforms: Smalltalk pure OOP, message-passing, class library and dynamism, coupled with the performance, features, native types and theoretical foundation of the substrate language. By deep design, essentially all native types of the substrate are visible to the Smalltalk layer as Immediates, *including the types the system is built with*. And likewise, all Smalltalk objects are visible and can be messaged from the substrate language, so the entire class library may eventually become available to programmers in the latter. The Smalltalk layer is intended as First Class Citizen, eventually fully self-contained, and programmers will not have to know the intermediate language at all. Knowing it will avail certain additional capabilities like defining new primitives on-the-fly, and fine tuned optimizing. * * * No release-able product is available at this time. There are major components and features remaining to be built, plus porting and development of class libraries. I estimate a timeframe of perhaps a couple years, maybe less, until an experimental release suitable for expert developers. However, the system is running on the bench with already many capabilities, including object model, dispatch, subclassing, core classes, Immediates, method definition, parallel thread fork, etc. There is a 50+ page Design Manual, and several 100s R&D notes. Measured performance: 160M+ sends/sec (peak seen is 210M+ sends/sec) actual dispatched sends (i.e. not inlined) to a standard object instance on the fastest code path (all cache hits) on a 1.6 GHz base i5-8265U (3.9 GHz boost). Optimizations like inlining, no lookup, fast accessors, etc, are designed and can yield even higher effective throughput. Plus the Nx parallel multiplier across N cores. == SEEK DONATING SUBSCRIBERS This system likely cannot be free or open-source, at least initially. It's extremely advanced, solves design challenges that other top minds in computing have not accomplished in 50 years, and has taken years of intensive research, design and development, unfunded, and personally funded and initiated. Prior Smalltalk parallel efforts involve greatly reduced single-core performance (e.g. RoarVM at 22%), or cumbersome multi-process approaches. Whereas this system is running at near 100% baseline on single core (ref. Squeak/Cog), transpiles at a high language level, and ultimately compiles to native machine code. If you are interested in this technology, I request you become a donating subscriber now, to reward my work to date, and encourage and fund bringing the system into existence and availability. I'm inclined to a subscriber model because I want you to have ongoing interest, and I intend that if and when the technology is ready for wider release, first consideration, news and availability will be offered to long-term subscribers in good standing (and you will be expected to continue funding under some subscription license terms and/or royalties) (but no guarantees in any case). You can of course alter or suspend your subscription at any time. Also I welcome and request your funding even if you don't have a personal immediate use for this system, or prefer a 1-time donation for now. A suggested contribution is 1% of your "seat" for individuals, or department headcount or project budget, with any amount appreciated. Please contact me with your contribution schedule and preferred channel, and indicate if you would like news updates. Thank you! I can accept most cryptocoins (preferred), or Paypal, bank wire transfers, mailed paper checks, or set up whatever service like Patreon / Ko-Fi you are familiar with. Note that you are making strictly a donation, gift, research and development grant, regardless of amount. It is not a purchase or investment, and does not entail any rights whatsoever -- not use, access, support or any other return. If you would like to do development work on this system, it's not ready for that, even if you are willing to contribute for free. There may be a tiered model in future with open-source class libraries you could work on. If your organization is interested in special license or acquiring the whole IP outright, it's in the realm of possible. Contact me with offers and inquiries, bearing in mind this is a high ehd design and system, which I believe advances the state-of-art, and there are few or zero precursors or comparable technologies available. A substantial non-refundable payment will be required to even start talking on this level, plus NDAs, so structure any dialog accordingly. Thank you for your consideration, and feel free to forward this message to other potential supporters. This is JBThiel. (Linux '92, and lots else). -- JBThiel jbthiel(a)gmail.com jbthiel(a)pobox.com (Paypal) Cryptocoin addresses avail on request. == FOOTNOTE: SPECIAL NOTE TO PROFESSORS / ACADEMICS If you are in academia, I request you to grant me some graduate degrees from your related programs. My work and this system solves challenges the industry at large has not achieved in 50 years. There are a number of extremely complex issues to making Smalltalk simultaneously multi-core, threadsafe, and high-performance, readily PhD level theses and beyond, and I believe to have identified and solved many or all of them with this design and implementation. For example, the esoteric #Become capability alone is a basket of theses, extremely complex to achieve safely and efficiently under multi-thread, non-stop-the-world conditions. It permeates and induces requirements across the entire system and object model. The ANSI Smalltalk Spec and prior technology does not even contemplate the semantics of such situations, let alone solutions. In this system I have worked out a meaningful semantics and robust, high performance approach to such cases, and others, that does not stop-world. I probably don't have time to write conventional papers for your department and publications. The substantiation of my theses is that no generally viable solutions have been produced by other top researchers and developers in the industry over prior decades, and this technology is now designed, built, and working on my bench. This work may be included by reference. I have a strong academic background, and experienced and expert in computing theory and practice, but don't have any doctorates yet despite completing most of a graduate program, due to the buffets of history and economy, plus the entire graduate institute I attended folded before I finished, and it irks me. I may actually make this a requirement for use by any professors or academics, so saddle your posse and grant me some PhD's or similar credential from your organization (can be honorary). As further incentive, I may offer a free license to your institution, or credits, promotion, or other benefits. Open to your suggestions and collaboration. Thank you for your consideration. -- JBThiel == DISCLAIMER NOTE CAREFULLY: There is no release-able product currently. There may never be. If there is, it may not be released to you, or at a suitable price or terms or capability for your purposes or expectations, regardless of your support or contribution level. The project could be dropped, encounter unsolvable difficulties, be sold to private investors, etc. The foregoing presentation, while believed correct, may contain errors in perspective, design, measurement, etc. You are being asked to support this author, research and development, with voluntary gifts, donations, research grants, with the sole motivation of rewarding efforts to date and encourage bringing the technology into existence, with no specific return to you of any kind. Your contribution is *not an investment, not a purchase*. There is no guarantee, rights, license or expectation of any product, results, profits, usage, news, access, priority, support, or any other return or interest of any kind for yourself, organization, or at large. == COPYRIGHT The foregoing material and announcement is Copyright 2026, JBThiel, all rights reserved, and may not be copied, modified or adapted for any purpose, except to support promotion and funding of this system and author. The mentioned softwares and designs are wholly owned confidential technologies of JBThiel. == END, PRE-PRE-ANNOUNCE

June 2, 2026

New VM Release - v12.0.2-beta

by Guille Polito

Hi all, We wanted to share a new VM release, aimed at Pharo 14 images. https://github.com/pharo-project/pharo-vm/releases/tag/v12.0.2-beta Besides many cleanups and small improvements, this enables a soon-to-come stack overflow support. For those interested in more details, I allowed myself to generate a digested changes log with some AI. Those using zeroconf will see this change effective immediately. Launcher users, do not forget to update your VMs. Please consider this is a beta release. Do not hesitate to communicate any issues you may find. Cheers, G Highlights This is a major release featuring: Frame unification and stack management improvements, delivering substantial interpreter and execution engine cleanups. RISC-V JIT support, expanding platform coverage and future-proofing VM development. New memory management capabilities, including direct old-space allocation and numerous GC and allocation improvements. Extensive compiler and Slang/C translation work, with many correctness fixes, new tests, and improved inspection tools. Platform and build modernization, including SDL updates, improved CI, cross-build support, and updated third-party dependencies. Large-scale cleanup and refactoring efforts across the VM, interpreter, Cogit, PICs, and infrastructure. VM Runtime, Interpreter & JIT Frame unification (#602 <https://github.com/pharo-project/pharo-vm/pull/602>) Improvements in stack management (#710 <https://github.com/pharo-project/pharo-vm/pull/710>) Initialize stack pages during simulation (#853 <https://github.com/pharo-project/pharo-vm/pull/853>) Robust cannotInterpret: in the interpreter (#641 <https://github.com/pharo-project/pharo-vm/pull/641>) Simplify stack-to-register mapping API (#627 <https://github.com/pharo-project/pharo-vm/pull/627>) Improve and use unreachable (#630 <https://github.com/pharo-project/pharo-vm/pull/630>) Clean up Interpreter State (#658 <https://github.com/pharo-project/pharo-vm/pull/658>) Void the instructionPointer systematically when creating a base frame (#914 <https://github.com/pharo-project/pharo-vm/pull/914>) Cleanup make base frame when compacting code (#943 <https://github.com/pharo-project/pharo-vm/pull/943>) Fix meta try primitive (#968 <https://github.com/pharo-project/pharo-vm/pull/968>) Feature: thisProcess JIT (#1037 <https://github.com/pharo-project/pharo-vm/pull/1037>) OpenPIC / Megamorphic IC work (#1067 <https://github.com/pharo-project/pharo-vm/pull/1067>) PIC Cleanup (#889 <https://github.com/pharo-project/pharo-vm/pull/889>) Cleanup PIC (#1021 <https://github.com/pharo-project/pharo-vm/pull/1021>) Allow Cogit>>#mnuMethodOrNilFor: to return non-CompiledMethod oops (#936 <https://github.com/pharo-project/pharo-vm/pull/936>) Remove entry alignment (#934 <https://github.com/pharo-project/pharo-vm/pull/934>) Mark debugging overrides in Cogit as #debuggerCompleteToSender (#1035 <https://github.com/pharo-project/pharo-vm/pull/1035>) Memory Management & Garbage Collection Do not unlink all sends on GC (#503 <https://github.com/pharo-project/pharo-vm/pull/503>) Improving perm space P12 (#621 <https://github.com/pharo-project/pharo-vm/pull/621>) Added new primitive for allocating directly in the old space (#701 <https://github.com/pharo-project/pharo-vm/pull/701>) Adding test to test Ephemerons in the Old Space (#702 <https://github.com/pharo-project/pharo-vm/pull/702>) Clean special object array a little (#640 <https://github.com/pharo-project/pharo-vm/pull/640>) Collapse allocation logs (#913 <https://github.com/pharo-project/pharo-vm/pull/913>) Only scan the class table if become: was performed to an active class object (#1023 <https://github.com/pharo-project/pharo-vm/pull/1023>) Set the size of larger indexable objects allocated in young space (#976 <https://github.com/pharo-project/pharo-vm/pull/976>) Fix LargeIntegers segfault on allocation failure (#1040 <https://github.com/pharo-project/pharo-vm/pull/1040>) Compiler, Slang & Code Generation Reject reserved words (#613 <https://github.com/pharo-project/pharo-vm/pull/613>) Rename reserved words: selectors, locals and instance variables (#624 <https://github.com/pharo-project/pharo-vm/pull/624>) Rename conflicting identifiers (#646 <https://github.com/pharo-project/pharo-vm/pull/646>) Validate if locals/args exist when adding a type declaration (#603 <https://github.com/pharo-project/pharo-vm/pull/603>) Check structs' instance variable type declarations (#607 <https://github.com/pharo-project/pharo-vm/pull/607>) Redundant type declaration linter rule (#662 <https://github.com/pharo-project/pharo-vm/pull/662>) Fix cast tests (#660 <https://github.com/pharo-project/pharo-vm/pull/660>) Fix and test inlinings with ifs and right shifts not translated (#667 <https://github.com/pharo-project/pharo-vm/pull/667>) Add tests and fix incorrectly generated inlined C code from CCodeGenerator (#666 <https://github.com/pharo-project/pharo-vm/pull/666>) C AST translation right-side parenthesis in expression (#685 <https://github.com/pharo-project/pharo-vm/pull/685>) Add a palette with the C translation of any inspected C node (#686 <https://github.com/pharo-project/pharo-vm/pull/686>) Add C source code inspection tab for TParseNode (#687 <https://github.com/pharo-project/pharo-vm/pull/687>) Created new package CAST-Tests (#679 <https://github.com/pharo-project/pharo-vm/pull/679>) Better dead code elimination (#915 <https://github.com/pharo-project/pharo-vm/pull/915>) Fix issue #822 <https://github.com/pharo-project/pharo-vm/issues/822>: remove unused argument for functionPointerFor:inClass: (#956 <https://github.com/pharo-project/pharo-vm/pull/956>) Fix CASTParserTests>>#testParseSizeofTypeInt (#965 <https://github.com/pharo-project/pharo-vm/pull/965>) Refactor inlining code and add tests for it (#987 <https://github.com/pharo-project/pharo-vm/pull/987>) Suppress the old inlining implementation (#1000 <https://github.com/pharo-project/pharo-vm/pull/1000>) Fix small bug related to method inlining and comments (#957 <https://github.com/pharo-project/pharo-vm/pull/957>) Remove the idea that we might have a different bytecode set (#927 <https://github.com/pharo-project/pharo-vm/pull/927>) Add a dumb isNotNil implementation (same as notNil) (#890 <https://github.com/pharo-project/pharo-vm/pull/890>) Platform Support & Portability RISC-V JIT Support (#932 <https://github.com/pharo-project/pharo-vm/pull/932>) Initial work on W^X for Linux systems (#905 <https://github.com/pharo-project/pharo-vm/pull/905>) Add Windows support for non-ASCII filenames in basicImageFileExists (#922 <https://github.com/pharo-project/pharo-vm/pull/922>) Fix the Windows build (#938 <https://github.com/pharo-project/pharo-vm/pull/938>) Windows improvements (#1062 <https://github.com/pharo-project/pharo-vm/pull/1062>) Make next non-blocking on Linux (#1065 <https://github.com/pharo-project/pharo-vm/pull/1065>) Support x86_64 musl cross-build smoke testing with QEMU (#1069 <https://github.com/pharo-project/pharo-vm/pull/1069>) Updating versions for OSX (ARM / Intel) (#937 <https://github.com/pharo-project/pharo-vm/pull/937>) Build System, CI & Dependencies Update SDL (#615 <https://github.com/pharo-project/pharo-vm/pull/615>) Remove strange SDL2_copy CMake target (#620 <https://github.com/pharo-project/pharo-vm/pull/620>) Forward VM build parameters from CMake (#654 <https://github.com/pharo-project/pharo-vm/pull/654>) Use Pharo 11 on CI (#669 <https://github.com/pharo-project/pharo-vm/pull/669>) Use Pharo file server @ Inria (#868 <https://github.com/pharo-project/pharo-vm/pull/868>) Extract full semantic version from git (#870 <https://github.com/pharo-project/pharo-vm/pull/870>) Remove old versions of libgit in new builds (#902 <https://github.com/pharo-project/pharo-vm/pull/902>) Update CMake minimal version for recent CMake compatibility (#945 <https://github.com/pharo-project/pharo-vm/pull/945>) Updating LibGit2 build to use new OpenSSL and libssh2 (#1033 <https://github.com/pharo-project/pharo-vm/pull/1033>) SDL2 2.32.6 update for Windows and macOS (#978 <https://github.com/pharo-project/pharo-vm/pull/978>) Fix OBS build (#981 <https://github.com/pharo-project/pharo-vm/pull/981>) Add FEATURE_JIT_SIMD option (#966 <https://github.com/pharo-project/pharo-vm/pull/966>) Fix Linux compilation error (#1053 <https://github.com/pharo-project/pharo-vm/pull/1053>) Plugins, I/O & Networking New file plugin (#1024 <https://github.com/pharo-project/pharo-vm/pull/1024>) Fix missing socket accept on Pharo 12 (#1005 <https://github.com/pharo-project/pharo-vm/pull/1005>) Move warnings to debug when loading plugins (#675 <https://github.com/pharo-project/pharo-vm/pull/675>) Testing & Simulation Small stack interpreter tests (#690 <https://github.com/pharo-project/pharo-vm/pull/690>) Simulator fixes (#1025 <https://github.com/pharo-project/pharo-vm/pull/1025>) Fix VM tests: specialObjectsArrayAddress (#1056 <https://github.com/pharo-project/pharo-vm/pull/1056>) Fix broken GC tests (#917 <https://github.com/pharo-project/pharo-vm/pull/917>) Fix some Slang tests (#891 <https://github.com/pharo-project/pharo-vm/pull/891>) Redo ML localization test fixes (#1064 <https://github.com/pharo-project/pharo-vm/pull/1064>) Bug Fixes Resolved UUID primitive bug (#610 <https://github.com/pharo-project/pharo-vm/pull/610>) Make instantiateClass more robust when format is missing (#629 <https://github.com/pharo-project/pharo-vm/pull/629>) Revert #629 <https://github.com/pharo-project/pharo-vm/pull/629> (#631 <https://github.com/pharo-project/pharo-vm/pull/631>) Revert the revert and restore primitive failure handling (#634 <https://github.com/pharo-project/pharo-vm/pull/634>) Add getClass for Pharo 12 compatibility (#651 <https://github.com/pharo-project/pharo-vm/pull/651>) Fix warning absolute value (#782 <https://github.com/pharo-project/pharo-vm/pull/782>) Fix load 32 bits (#920 <https://github.com/pharo-project/pharo-vm/pull/920>) Fix headerAt:put: (#919 <https://github.com/pharo-project/pharo-vm/pull/919>) Fix sign coercion warnings (#950 <https://github.com/pharo-project/pharo-vm/pull/950>) Fix int boxing/loading (#1066 <https://github.com/pharo-project/pharo-vm/pull/1066>) VM version primitive (#1050 <https://github.com/pharo-project/pharo-vm/pull/1050>) Profile data extraction from PIC cache tags (#969 <https://github.com/pharo-project/pharo-vm/pull/969>) Refactoring, Cleanup & Maintenance Added comments and renamed methods during dojo (#623 <https://github.com/pharo-project/pharo-vm/pull/623>) Fixing categorization P12 (#626 <https://github.com/pharo-project/pharo-vm/pull/626>) Updating P12 with changes from P10 branch (#733 <https://github.com/pharo-project/pharo-vm/pull/733>) Forward porting P10 â P12 (#851 <https://github.com/pharo-project/pharo-vm/pull/851>) Forward port 10 â 12 (#893 <https://github.com/pharo-project/pharo-vm/pull/893>) Forward port 10.3.3 â Pharo 12 (#903 <https://github.com/pharo-project/pharo-vm/pull/903>) Realign P12 branch to P10 (#1057 <https://github.com/pharo-project/pharo-vm/pull/1057>) Removing duplicated code (#857 <https://github.com/pharo-project/pharo-vm/pull/857>) Cleanups and improvements (#871 <https://github.com/pharo-project/pharo-vm/pull/871>) Lots of cleanups (#874 <https://github.com/pharo-project/pharo-vm/pull/874>) Cleaning (#881 <https://github.com/pharo-project/pharo-vm/pull/881>) Cleanup dead code (#961 <https://github.com/pharo-project/pharo-vm/pull/961>) Cleanup warnings (#906 <https://github.com/pharo-project/pharo-vm/pull/906>) Fix warnings (#1034 <https://github.com/pharo-project/pharo-vm/pull/1034>) Remove debugging code (#911 <https://github.com/pharo-project/pharo-vm/pull/911>) Remove unused variables (#930 <https://github.com/pharo-project/pharo-vm/pull/930>) Normalize variable (#897 <https://github.com/pharo-project/pharo-vm/pull/897>) Remove gcMode because getGCMode is used (#963 <https://github.com/pharo-project/pharo-vm/pull/963>) Remove ceShortCutTraceStore: and simulation guard users (#960 <https://github.com/pharo-project/pharo-vm/pull/960>) Simplify signal handler space calculation using POSIX SIGSTKSZ (#910 <https://github.com/pharo-project/pharo-vm/pull/910>) Documentation & Developer Experience README: Developer documentation is not a link (#637 <https://github.com/pharo-project/pharo-vm/pull/637>) Update README (#878 <https://github.com/pharo-project/pharo-vm/pull/878>) Add default values to --help parameters (#872 <https://github.com/pharo-project/pharo-vm/pull/872>) Fix typos in comments (#958 <https://github.com/pharo-project/pharo-vm/pull/958>) New Contributors @Mathilde411 <https://github.com/Mathilde411> @LucFabresse <https://github.com/LucFabresse> @ivojawer <https://github.com/ivojawer> @Gabriel-Darbord <https://github.com/Gabriel-Darbord> @iglosiggio <https://github.com/iglosiggio> @rolandbernard <https://github.com/rolandbernard> @fouziray <https://github.com/fouziray> @kilian-kier <https://github.com/kilian-kier> @NathanMalenge <https://github.com/NathanMalenge> @FedeLoch <https://github.com/FedeLoch> @Ducasse <https://github.com/Ducasse> @takano32 <https://github.com/takano32>

June 2, 2026

ANN: Experimental flatpak pharo vm v10.3.9

by Esteban Lorenzano

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

June 2, 2026

Re: "My First Pair Programming Session with Claude in Pharo" â New blog post on all: objects all: theTime

by steven.costiou＠kloum.io

Hi, it's really minor that AI can hallucinate, destroy your database, produce bad code and a whole new generation of unskilled sloppy coders, and among other things, make you dumb. Despite that AI can still do impressive things. But why would you use AI when you know its tremendous ecological (especially water consumption and heat production) and sociological cost? What about: stop paying for AI, stop funding AI, take back the money from OpenAI and all (they have too much) and let's correctly train powerful new programmers to become our cool future colleagues, all without giant data-centers that consume whole cities' resources? And I don't think that these questions cannot be answered in a productive way and unheated (ha ha) way. Steven. Le 2026-05-29 10:16, Danil Osipchuk a Ã©crit : > Koen, greetings > > Thank you for your consistent effort with your blog, it is a pleasure > to read. > > With AI there are many facets, some of which are more controversial > than others, this list seems to politely stay silent to avoid heated > unproductive discussions. > However, I can't help not to suggest the story here > https://www.theguardian.com/technology/2026/apr/29/claude-ai-deletes-firm-d… > and the observation that the agent's explanation why it did delete the > database sounds like a bold metaphysical statement. > > Fun times. > > regards, > Danil > > ÑÑ, 28 Ð¼Ð°Ñ 2026â¯Ð³. Ð² 00:13, Koen De Hondt > <koen(a)all-objects-all-the-time.st>: > >> Dear Pharo users and developers, >> >> I posted the third article in a series about using AI in Pharo >> development. After building the MCP server together, it was time to >> pair program with Claude to write some code in a Pharo image. In the >> new post, I share my experience of working with Claude and how it has >> impacted my development process. >> >> https://all-objects-all-the-time.st/#/blog/posts/26 >> >> As always, all feedback is welcome. >> >> Happy reading! >> >> Ciao, >> Koen

May 29, 2026