August 2026 - 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