May 2025 - Esug-list - lists.esug.org

Fwd: [Pharo-users] [ANN] Pharo 13 Released!
by stephane ducasse May 26, 2025

May 26, 2025

I want to thank all the people that make this happening… The list of commits at the end is impressive but it is only for one repository: the one of Pharo and it does not take into account all the subprojects. Thanks you all. S. > Begin forwarded message: > > From: Esteban Lorenzano via Pharo-users <pharo-users(a)lists.pharo.org> > Subject: [Pharo-users] [ANN] Pharo 13 Released! > Date: 23 May 2025 at 08:56:59 CEST > To: pharo-users(a)lists.pharo.org, pharo-dev(a)lists.pharo.org > Cc: Esteban Lorenzano <estebanlm(a)netc.eu> > Reply-To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > > Dear Pharo users and dynamic language lovers: > > We have released Pharo <https://pharo.org/> version 13! > > What is Pharo? > > Pharo is a pure object-oriented programming language and a powerful environment focused on simplicity and immediate feedback. > > Simple & powerful language: No constructors, no types declaration, no interfaces, no primitive types. Yet a powerful and elegant language with a full syntax fitting in one postcard! Pharo is objects and messages all the way down. > Live, immersive environment: Immediate feedback at any moment of your development: Developing, testing, debugging. Even in production environments, you will never be stuck in compiling and deploying steps again! > Amazing debugging experience: Pharo environment includes a debugger unlike anything you’ve seen before. It allows you to step through code, restart the execution of methods, create methods on the fly, and much more! > Pharo is yours: Pharo is made by an incredible community, with more than 100 contributors for the last revision of the platform and hundreds of people constantly contributing with frameworks and libraries. > Fully open-source: Pharo full stack is released under MIT <https://opensource.org/licenses/MIT> License and available on GitHub <https://github.com/pharo-project/pharo> > … more on the Pharo Features page <http://www.pharo.org/features>. > In this iteration of Pharo, we continue working on our objectives of improvement, clean-up and modularization. > Also, we included a number of usability and speed improvements. > A detailed list of changes and improvements is available in our Changelog <https://github.com/pharo-project/pharo-changelogs/tree/master/weekly> (weekly based) > > Some highlights of this amazing version: > > Highlights > > Tools > > Spec Tools remembering their size > Microdown enhancements > HDPI support > Zoomable UI > New list, tables and trees, allowing any presenter as their content > Better source code text navigation and edition > New Process Browser > New Transcript (introducing also the Object Transcript) > Organic window manager > System > > Better refactorings UX Cleaner leaner code logic > More robust and faster halt implementation > Debug points to enhance the debugging experience > Clean-ups > Virtual machine > > Async IO using epoll on unixes > Faster byte array / string comparisons > Improve Windows support for non ASCII filenames > FreeBSD support > Update SDL2 version in OSX (Intel & Apple) > Minimal MacOS version required raised to MacOS 11 and above > Development Effort > > This new version is the result of 698 Pull Requests integrated just in the Pharo repository. > We have closed 865 issues and received contributions from more than 70 different contributors. > We also have a lot of work in the separate projects that are included in each Pharo release: > > http://github.com/pharo-spec/NewTools > http://github.com/pharo-spec/Spec > http://github.com/pharo-vcs/Iceberg > https://github.com/pharo-graphics/Roassal > http://github.com/pillar-markup/Microdown > http://github.com/pillar-markup/BeautifulComments > http://github.com/pharo-project/pharo-vm > Contributors > > We always say Pharo is yours. It is yours because we made it for you, but most importantly, because it is made by the invaluable contributions of our great community (yourself). > A large community of people from all around the world contributed to Pharo 13.0 by making pull requests, reporting bugs, participating in discussion threads, providing feedback, and a lot of helpful tasks in all our community channels. > Thank you all for your contributions. > > The Pharo Team > > Discover Pharo: https://pharo.org/features > > Try Pharo: http://pharo.org/download > > Learn Pharo: http://pharo.org/documentation > Stéphane Ducasse http://stephane.ducasse.free.fr 06 30 93 66 73 "If you knew today was your last day on earth, what would you do differently? ....ESPECIALLY if, by doing something different, today might not be your last day on earth.” Calvin & Hobbes

1 1

Camp Smalltalk @ ESUG 2025
by Marcus Denker May 21, 2025

May 21, 2025

Hello, There will be again a chance to organize a meeting for the days before / after the conference. I have setup a form so we know who is interested. https://app.apptivegrid.de/api/r/6229d48b322a681a3a99ce35/66437a609e4bc228c… The plan for now is: - get a room for Sat-Monday at the university, - for the day after we need those interested to find a place Marcus

1 0

Survey: Identifying and Fixing Undesirable Behaviors Across Software Versions
by Remi Dufloer May 12, 2025

May 12, 2025

Hello, As part of my PhD at the University of Lille, I am currently conducting a study on how developers handle certain bug scenarios. The goal is to better understand current practices, the tools used, and developers' needs regarding debugging in a specific scenario. Link to the questionnaire: [ https://sondages.inria.fr/index.php/566958?lang=en | https://sondages.inria.fr/index.php/566958?lang=en ] Your participation in this short questionnaire (5 - 10 minutes) would greatly help us analyze existing methods and identify potential gaps in the available solutions. This survey will be open for 6 weeks (Until May 15th, 2025) . The responses will be analyzed and included in a scientific publication. The results will be available [ https://remidufloer.github.io/Dufloer.github.io/survey.html | here ] . If you can, please feel free to share this questionnaire with other developers who might be interested. Every response counts and will contribute to a better understanding of the community's practices! A big thank you for your help and time. Best regards, Rémi Dufloer PhD Student, University of Lille ------------------------------------------------ ------------------------------------------------ ------------------------------------------------ ------------------------------------------------ ------------------------------------------------ Bonjour , Dans le cadre de ma thèse à l’Université de Lille, je mène actuellement une étude sur la manière dont les développeurs gèrent certains scénarios de bugs. L’objectif est de mieux comprendre les pratiques actuelles, les outils utilisés et les besoins des développeurs en matière de debugging sur un scénario précis. Voici le lien du questionnaire : [ https://sondages.inria.fr/index.php/566958?lang=en | https://sondages.inria.fr/index.php/566958?lang=en ] Votre participation à ce court questionnaire (5 - 10 minutes) nous aiderait énormément à analyser les méthodes existantes et à identifier les éventuelles lacunes dans les solutions disponibles. Ce survey est ouvert durant 6 semaines (fermeture le 15 mai 2025 ). Les réponses obtenues seront analysées et feront l'objet d'une publication scientifique. Les résultats seront publiés [ https://remidufloer.github.io/Dufloer.github.io/survey.html | ici ] . Si vous le pouvez, n’hésitez pas à partager ce questionnaire avec d’autres développeurs susceptibles d’être intéressés. Chaque réponse compte et contribuera à une meilleure compréhension des pratiques de la communauté ! Un grand merci pour votre aide et votre temps. Bien cordialement, Dufloer Rémi Doctorant, Université de Lille

1 2

Call for Participation: SLE 2025 - 18th ACM SIGPLAN International Conference on Software Language Engineering
by Andrei Chis May 8, 2025

May 8, 2025

** Call for Participation ** 18th ACM SIGPLAN International Conference on Software Language Engineering (SLE 2025) 12-13 June 2025 Koblenz, Germany https://conf.researchr.org/home/sle-2025 https://www.sleconf.org/2025/ https://x.com/sleconf ------------------------------------------------------------------------ The ACM SIGPLAN International Conference on Software Language Engineering (SLE) is devoted to the principles of software languages: their design, their implementation, and their evolution. Like its predecessors, the 18th edition of the SLE conference, SLE 2025, will bring together researchers from different areas united by their common interest in the creation, capture, and tooling of software languages. It overlaps with traditional conferences on the design and implementation of programming languages, model-driven engineering, and compiler construction, and emphasises the fusion of their communities. To foster the latter, SLE traditionally fills a two-day program with a single track, with the only temporal overlap occurring between co-located events. --------------------------- Registration --------------------------- Registration happens via the STAF registration page Early Bird Registration Deadline is May 10th, 2025 https://conf.researchr.org/attending/staf-2025/staf-2025-registration --------------------------- Venue --------------------------- University of Koblenz https://conf.researchr.org/venue/sle-2025/staf-2025-venue --------------------------- Keynotes --------------------------- * Thorsten Berger, Ruhr University Bochum, Germany A New DSL Textbook in Town! * Friedrich Steimann, Fernuniversität in Hagen, Germany an Programming Be Liberated from the Functional Style? https://conf.researchr.org/home/sle-2025#Keynotes --------------------------- Awards --------------------------- During the conference, we will announce the following awards: * Distinguished paper: Award for the most notable paper, as determined by the PC chairs based on the recommendations of the program committee. * Distinguished artefact: Award for the artefact most significantly exceeding expectations, as determined by the AEC chairs based on the recommendations of the artefact evaluation committee. * Distinguished reviewer: Award for the programme committee member that produced the most useful reviews as assessed by paper authors. * Most Influential Paper: Award for the SLE 2015 paper with the greatest impact, as judged by the SLE Steering Committee. * COLA Award: 2024 Journal of Computer Languages Best Paper Award --------------------------- Accepted Papers --------------------------- * A Model-Driven Approach to Design, Generation, and Deployment of GUI Component Libraries Arkadii Gerasimov, Nico Jansen, Judith Michael, Bernhard Rumpe, Sebastian Will * AnyText: Incremental, left-recursive Parsing and Pretty-Printing from a single Grammar Definition with first-class LSP support Georg Hinkel, Alexander Hert, Niklas Hettler, Kevin Weinert * Boosting Parallel Parsing through Cyclic Operator Precedence Grammars Michele Chiari, Michele Giornetta, Dino Mandrioli, Matteo Pradella * Detecting Resource Leaks on Android with Alpakka Gustavo Amorim Santos, Alexandra Mendes, João Bispo * Dynamic Dependency-Based Purity Checking Anton Risberg Alaküla, Niklas Fors, Christoph Reichenbach * Exploratory, Omniscient, and Multiverse Diagnostics in Debuggers for Non-Deterministic Languages Damian Frölich, Tommaso Pacciani, L. Thomas van Binsbergen * Handling Grammar Cycles in the 1997 Standard ML Definition Elizabeth Scott, Adrian Johnstone * Integrating Model Checking into a Live Modeling Environment Joeri Exelmans, Ciprian Teodorov, Hans Vangheluwe * Lessons Learned: Challenges of Modular Language Design Alex Lüpges, Nico Jansen, Bernhard Rumpe * Optimal Language Design is Hard: A Case Study in ECMAScript (JavaScript) Standardization Philipp Riemer, Yury Nikulin, Ashley Claymore, Mikhail Barash * Optimize Effect Handling for Tail-resumption with Stack Unwinding Yuze Fu, Shigeru Chiba * Property-based Testing of Attribute Grammars José Nuno Macedo, Marcos Viera, João Saraiva * Scheduling the Construction and Interrogation of Scope Graphs Using Attribute Grammars Luke Bessant, Eric Van Wyk * (Semantic) Feature Model Differences with (Q)SAT Simone Heisinger, Maximilian Heisinger, Martina Seidl * TranspileJS, an Intelligent Framework for Transpiling JavaScript to WebAssembly José Pedro Ferreira, João Bispo, Susana Lima * Variability Fault Localization by Abstract Interpretation and its Application to SPL Repair Aleksandar S. Dimovski

1 0

Re: IWST Logo selection
by Luc Fabresse May 6, 2025

May 6, 2025

Hello, Nice and I also like the 1st one (hot air balloon) and yes the font used for IWST should be changed IMO. Cheers, #Luc Le mer. 30 avr. 2025 à 18:04, 'David Mason' via ESUG Board <board(a)esug.org> a écrit : > The first 2 look great to me. > > ../Dave > > On Wed, 30 Apr 2025 at 10:16, Santiago Bragagnolo < > santiagobragagnolo(a)gmail.com> wrote: > >> my 2 cents: the logos on the first two pages, if you read fast without >> paying attention you may read lust instead of iwst (at least it happened to >> me). I like them specially the first one, however, me I would change maybe >> the case of the i to ensure it is understood as an i. >> >> >> >> >> El mié, 30 abr 2025 a las 15:07, Guillermo Polito (< >> guillermopolito(a)gmail.com>) escribió: >> >>> Hello board, >>> >>> For the IWST logo, we launched last year a competition. >>> We received several submissions, we filtered the “ugly” ones. >>> >>> The PDF below shows a selection of three, ranked by our preferences. >>> (First one is our preferred one). >>> >>> We need from you: >>> >>> - validating/voting for the one we should use, as this logo will >>> represent ESUG too. We prefer the first one, but we are open to suggestions. >>> >>> - to know if you have some proposals or modifications. We are thinking >>> on asking some font changes, probably you have some extra requirements like >>> color or so... >>> >>> - we talked last year a prize of 200€. Is that still ok? We could give >>> it during the social event in the conference. >>> >>> Cheers, >>> G & G >>> >>> >>> _______________________________________________ >>> Esug-list mailing list -- esug-list(a)lists.esug.org >>> To unsubscribe send an email to esug-list-leave(a)lists.esug.org >>> >> _______________________________________________ >> Esug-list mailing list -- esug-list(a)lists.esug.org >> To unsubscribe send an email to esug-list-leave(a)lists.esug.org >> >

4 3