- Pharo-users - lists.pharo.org

Benchmarks/Tests for Base Image
by Steffen Märcker Aug. 18, 2026

Aug. 18, 2026

Hi! I presented my work on Transducers at IWST recently and I am preparing the final version of the corresponding paper. A week spot of that work is in the evaluation: I replaced the common enumeration methods like select: and collect: with versions using transducers. The image ran stable and I observed no perceptible slowdowns. However, I'd very much like to back this anecdotal evidence with some real data or measurements. Hence: Are you aware of a publicly available benchmark or test suite for the base VW image? Or something covering the common enumeration protocol? Do you have an alternative idea? (Same goes for Pharo at a later date.) Happy coding! Steffen

2 2

Re: [Esug-list] All Smalltalk Report PDF archive online
by Sean DeNigris Aug. 14, 2026

Aug. 14, 2026

> I just published all the archive of the old Smalltalk reports I found on my disc: this is nice to be able to browse all such small (yet interesting) articles around Smalltalk (91-96) Wow, thanks! This is sooo cool :) There were some extra chars in the URL; this one works: https://github.com/Ducasse/SmalltalkReportPDFArchive

3 2

Looking for my next Smalltalk opportunity
by Sebastian Jordan Aug. 5, 2026

Aug. 5, 2026

Hi everyone, After almost seven years being part of the Pharo community, I wanted to reach out here because this community has been an important part of my professional journey. I am currently finishing my PhD at INRIA, France, and I am looking for my next opportunity as a software developer. After completing my PhD, I will be moving back to LATAM, Bolivia, and I am looking for a fully remote position starting around mid-October or November. I would love to continue working with Smalltalk. Most of my experience is with Pharo, but I am open to any Smalltalk dialect and different kinds of projects. I am also open to full-time positions, contracts, or consulting work. Over the years, I have contributed to several parts of the Pharo ecosystem. Before my PhD, I worked as an R&D software engineer at INRIA on Pharo, where I developed tools for code analysis and transformation, contributed to Moose and pharo-ai. I have mentored students through Google Summer of Code since 2021. I have continued to work on programming languages and developer tools throughout my PhD, focusing on runtime-related issues, instrumentation, profiling (dynamic analysis), and memory analysis. Solving difficult problems, designing clear object-oriented systems, writing tests, improving existing codebases through refactoring, and building tools that increase developer productivity are all aspects of software development that I enjoy. I also enjoy working on enterprise applications where maintainability and good design are important. If you know of a team looking for someone with my background, or if you would simply like to discuss possible opportunities, I would be very happy to hear from you. I can also send my CV privately to anyone interested. Thanks everyone for your help, and I hope to continue being part of the Smalltalk community. Best regards, Sebastian JORDAN MONTAÑO

1 0

OpenAPI now validates and tracks JSONSchema master
by Norbert Hartl Aug. 1, 2026

Aug. 1, 2026

Hi all, OpenAPI (https://github.com/zweidenker/OpenAPI) got the same treatment as JSONSchema recently: the baseline dropped its stale 2020-era JSONSchema pin and now tracks JSONSchema's master, and the library actually validates whole documents now instead of just parsing them. What's new: OADocumentValidator checks a full document against the official OAI 3.0 meta-schema (bundled, Apache-2.0), with real error messages, not just true/false. Verified against six real OpenAPI 3.0 documents from the official spec repo (petstore, petstore-expanded, api-with-examples, callback-example, link-example, uspto) - round-tripping them surfaced and fixed several real bugs that hand-written test documents never would have. OpenAPI-Client was exercised against a real spec (Stripe's) end-to-end, which is what it took to find that request bodies were JSON-only when most real APIs use form-urlencoded bodies. That's fixed too. Scope is still explicitly OpenAPI 3.0. 3.1/3.2 use a different schema dialect (JSON Schema 2020-12 + OAS vocabulary - $dynamicRef, $ref-with-siblings, unevaluated*), which needs machinery JSONSchema doesn't have yet. Not pursuing that for now is a deliberate decision, not an oversight. Code and README (installation, quick start, what's not supported) are on GitHub: https://github.com/zweidenker/OpenAPI Norbert

1 0

Pharo Mailinglist moved to new setup: pharo-users@lists.pharo.org
by Marcus Denker July 30, 2026

July 30, 2026

We have moved the Pharo Mailinglists to a new setup. If you see this mail, you are subscribed to the mailinglist pharo-users(a)lists.pharo.org WARNING: We sadly could not migrate the settings for the subscribers (e.g. Digest) Even though you are subscribed, you can create an *account* to manage settings / see all lists you are in. For this, sign up at http://lists.pharo.org/accounts/signup to create an account and configure the lists as you need them. (This is optional but recommended) WARNING: one state *not* migrated includes "NO MAIL", this was used e.g. by people to send with different From:, but in addition, it seems that the old system did put subscribers with delivery problems in this state (without anyone getting notified). If you do not want to be in this list, please unsubscribe, see footer or just send a mail to me, I will remove you. Marcus

1 0

Pillar loaded for Pier
by John Borden July 30, 2026

July 30, 2026

Since this address shows up as "any question is welcome" I thought asking here may help. I have a couple small updates for Pillar (email addresses and testing package load order, and I’ve ran into issues since the Dev-8 branch of Pillar-Markup loads the Dev-7 branch of Pillar core. Is anyone aware of why this is setup this way? In testing a change to make them consistent I wound up with a pier image that had every link point to root. I’m still working through the failed tests but was hoping someone would remember why this is configured like that. Thanks, John

1 0

[ANN] Soil v5
by Norbert Hartl July 29, 2026

July 29, 2026

We are happy to announce the availability of Soil version 5. What is new? Automatic change tracking: Soil now computes a recursive content hash for objects and uses it to detect modifications automatically. This removes the need for the explicit markDirty: calls that were previously required — something we called out as a goal back in the v4 announcement. Read-only transactions have been hardened: we now distinguish a transaction that is intentionally read-only from one that just happens to end up with no changes, and read-only transactions abort automatically instead of committing a no-op. Indexed collections (SoilPersistentDictionary and indexed dictionaries) can now be used as non-root objects, not just at the root of the database. A first working garbage collector has landed — a preview, not a finished feature: Soil>>garbageCollect compacts object segments offline by cloning and atomically swapping them in. There's also a new opt-in Soil>>checkConsistency you can run separately without slowing down the GC itself. The data-layer primitives for a future online/segment-based GC are also in place, though not yet wired up. A new SoilCommitError hierarchy lets you catch any commit-time failure with one exception class instead of several unrelated ones. A good number of crash and silent-data-corruption fixes, notably around the graph exporter/importer, backup version history, and depth-first traversal. Full changelog: https://github.com/ApptiveGrid/Soil/blob/main/docs/versions/changelog-v5.md I also wrote up the release on the blog, with a bit more context: https://norbert.hartl.name/blog/2026-07-29_soil-v5-released.html What is planned next? Integrating the Windows support work that's already sitting there Process-specific variables A preview of an online GC, building on the primitives that landed in v5 Multi-index collections and partial indexes (carried over from v4's plan) Hope you like it. Give it a spin and then tell us! Norbert & Marcus

1 0

[ANN] JSONSchema: bringing test suite conformance up
by Norbert Hartl July 28, 2026

July 28, 2026

Hi , quick announcement: JSONSchema (https://github.com/zweidenker/JSONSchema) just got a real conformance push against the official Test-Suite (https://github.com/json-schema-org/JSON-Schema-Test-Suite) Udo ported that suite into Pharo a while back — over 1000 individual test methods — but it sat mostly unexplored until now. Claude and me went through it bucket by bucket and moved from roughly a third of the suite genuinely passing to about two-thirds: boolean schemas, oneOf/anyOf/not/pattern, dependencies, const, contains, patternProperties, if/then/else, tuple-shaped items, and a long list of format validators. For more information I’ve wrote an article: https://norbert.hartl.name/blog/2026-07-28_jsonschema-picked-back-up.html Feedback welcome, as always. Norbert

1 0

Mailinglists: Moving to new system
by Marcus Denker July 28, 2026

July 28, 2026

Hi, We are moving the Pharo lists to a new setup. I will send another mail when this is done (end of the week latest). The lists will continue to work, but the archives will be migrated with a certain export date (I guess today). Marcus

1 0

[ANN] pharo-cig FFI bindings for libcurl
by Esteban Lorenzano July 14, 2026

July 14, 2026

Hello, I am publishing bindings for libcurl at pharo-cig. Technically, this is not new as I generate the recipe and the bindings almost one year ago... but I forgot to commit it, as it was made while making tests on how to handle variadics :) I think the library can be useful, even if we do not need it for most common cases (we already have Zinc/Zodiac to handle downloads), but it may be useful in certain cases (e.g. to download in parallel, without putting pressure in the image, etc.). libcurl bindings are now part of the garden: https://github.com/pharo-cig/pharo-libcurl Esteban

1 0