- Esug-list - lists.esug.org

Re: [Pharo-users] Looking for Metacello beta testers

by Domenico Cipriani

Hello, I would like to help. what should I do? Load all my packages in a new Pharo 14 alpha and check if everything works? best. d On Mon, Dec 29, 2025 at 9:56 AM stephane ducasse via Pharo-users < pharo-users(a)lists.pharo.org> wrote: > Hello > > Under the radar, we are actively continiously cleaning Pharo deep core so > that we can work > on new features. > > For metacello, in Pharo 13 we introduced a strict mode (so that we can > detect hidden dependencies), > and other loading features to support module experimentations. It will > make Pharo code more robust > in the long term. > > Since a couple of months we are actively simplifying/cleaning Metacello > (as the version available in Pharo) because we want to introduce new > features such as the possibility to force the reload of baselines and > others. > > Now the unit test coverage of metacello is quite low and we do not > use/know all the features > that are available and that you may rely on. > > So we would love to have beta testers that can just try to load their code > in Pharo 14 alpha > and report potential bugs or features drop we would have introduced. > > So do not hesitate and this is a nice way to help pharo > > S.

Dec. 29, 2025

Looking for Metacello beta testers

by stephane ducasse

Hello Under the radar, we are actively continiously cleaning Pharo deep core so that we can work on new features. For metacello, in Pharo 13 we introduced a strict mode (so that we can detect hidden dependencies), and other loading features to support module experimentations. It will make Pharo code more robust in the long term. Since a couple of months we are actively simplifying/cleaning Metacello (as the version available in Pharo) because we want to introduce new features such as the possibility to force the reload of baselines and others. Now the unit test coverage of metacello is quite low and we do not use/know all the features that are available and that you may rely on. So we would love to have beta testers that can just try to load their code in Pharo 14 alpha and report potential bugs or features drop we would have introduced. So do not hesitate and this is a nice way to help pharo S.

Dec. 29, 2025

[DEBT 2026] Future Debugging Techniques Call for Papers, submission 7th of March 2026

by Steven Costiou

DEBT 2026: Call for Papers ================================================================================ DEBT 2026, Workshop co-located with ECOOP 2026, Brussels, Belgium Fourth Workshop on Future Debugging Techniques (https://2026.ecoop.org/home/debt-2026#Call-for-Papers) ================================================================================ Important Dates ----------------------- * Abstract submission deadline: Sat 28 Feb 2026 * Paper submission deadline: Sat 7 Mar 2026 * Author notification: Wed 15 Apr 2026 * Workshop: Monday 29 June 2026 ================================================================================ DEBT’26 is looking to advance state-of-the-art to debug modern software. We welcome researchers from all related areas aimed at helping with the hard task of diagnosing the root cause of bugs, including dynamic and static debugging techniques, online and postmortem debuggers, delta debugging, automatic bug finding, novel visualization techniques for debugging programs, etc. The workshop aims to gather the community and foster discussion from different perspectives. That is why we seek submissions in the form of papers as well as talks and tool demonstrations. The workshop is a venue for all approaches to debugging. A non-exclusive list of topics of interest is: * Debugging techniques, from static to dynamic techniques. * Innovative visualisation techniques. * Techniques targeted specific programming models and execution models (e.g., concurrent and parallel programming, microservices, distributed ledgers, web, etc. ) or hardware (e.g., debugging micro-controllers, mobile devices, Big Data applications, etc.). * Case studies and evaluation of such techniques, e.g., user studies on visualisation tools, debuggers, etc. * Surveys, taxonomies of bugs and bug patterns, and current practices/uses of debugging approaches. Papers must be formatted according to the guidelines for ACM sigplanpapers (\documentclass[sigplan,screen]{acmart}), seehttps://www.sigplan.org/Resources/Author/ <https://www.sigplan.org/Resources/Author/>for details. Submissions should be made via Easychair using the following link:https://easychair.org/conferences/?conf=debt2026 <https://easychair.org/conferences/?conf=debt2026> The accepted papers will be published in the ACM Digital Library, though authors will be able to opt out of this publication, if desired. At least one author of an accepted paper must register for the workshop and attend the event to present the work, and participate in the discussions. AUTHORS TAKE NOTE: The official publication date is the date the proceedings are made available in the ACM Digital Library. This date may be up to two weeks prior to the first day of your conference. The official publication date affects the deadline for any patent filings related to published work. Workshop Organizers --------------------------- * Burcu Kulahcioglu Ozkan, Delft University of Technology, Netherlands * Steven Costiou, Centre Inria de l’Université de Lille, France For more information see: https://2026.ecoop.org/home/debt-2026

Dec. 24, 2025

[SCLIT 2026] Call for Papers, submission deadline: 5th of January 2026

by Gordana Rakic

*Dear Colleagues and Friends ,* *** * * We would like again to draw your attention to the SCLIT symposium <http://www.sclit.org> and its 10th edition that will take place in Munich, Germany, between Mon 16 - Fri 20 March 2026 <https://2026.programming-conference.org/home/sclit-2026>. That will be hosted again by the <Programming> conference. <https://2026.programming-conference.org/series/programming> While organizers of <Programming> will make organizational decisions, the symposium keeps its academic autonomy. ** The symposium is devoted to the various aspects of computer languages and their roles in software engineering, science, education, etc. Submissions that describe work in progress and provoke discussions and position papers are also welcome. SCLIT welcomes submissions that are the result of original and unpublished research. The scope of the workshop is wide and versatile within the theme of computer languages. Particularly, SCLIT invites papers that include, but are not limited to the following topics: - Languages: theoretical aspects of programming languages, programming paradigms, script languages, modelling languages, domain-specific languages, graphical languages, markup languages, specification languages, transformation languages, formal languages, intermediate languages… - Implementations: Compilers, debuggers, interpreters, virtual machines, transformation systems, translators, transpilers, intermediate representations, … - Tools: software metrics, static analyzers, clone detectors, abstract interpreters, visualizers, … We especially encourage submissions addressing problems encompassing multiple languages in a language-independent or cross-language manner. Paper contributions should not exceed 8 pages, including all figures, tables, and bibliography, following theACM primary two-column article template <https://www.acm.org/publications/authors/submissions>. We receive your submissions at the EasyChair submission page <https://easychair.org/conferences/?conf=sclit2026>, where *they will be further managed *. All submissions will be peer-reviewed by at least three members of the international program committee. Accepted submissions will be published as part of the <Programming> conference companion proceedings that will be published in the ACM Digital Library. *The submission deadline is the 5th of January 2026.* Call for Papers: https://2026.programming-conference.org/home/sclit-2026 Symposium info with history:http://www.sclit.org <http://www.sclit.org> Conference site: https://2026.programming-conference.org/ <https://2026.programming-conference.org/> We apologize for cross-posting and kindly ask you to forward this information to all interested persons. Best regards and thank you, Gordana and SCLIT team *

Nov. 26, 2025

CfP: SLE 2026 - 19th ACM SIGPLAN International Conference on Software Language Engineering

by Andrei Chis

19th ACM SIGPLAN International Conference on Software Language Engineering (SLE 2026) 2 - 3 July 2026 Rennes, France https://conf.researchr.org/home/sle-2026 https://www.sleconf.org/2026/ ------------------------------------------------------------------------ We are pleased to invite you to submit papers to the 19th ACM SIGPLAN International Conference on Software Language Engineering (SLE) which is devoted to the principles of software languages: their design, their implementation, and their evolution. The SLE 2026 conference will be co-located with STAF 2026 and hosted in Rennes, France, on 2 - 3 July 2026. --------------------------- Important Dates --------------------------- * Abstract submission (all tracks): Friday 27 February 2026 * Paper submission (all tracks): Friday 6 March 2026 * Paper notification (all tracks): Monday 20 April 2026 * Conference: Thursday 2 - Friday 3 July 2026 (co-located with STAF) All dates are Anywhere on Earth. --------------------------- Topics of Interest --------------------------- SLE covers software language engineering in general, rather than engineering a specific software language. Topics of interest include, but are not limited to: *Software Language Design and Implementation - Approaches to and methods for language design - Static semantics (e.g., design rules, well-formedness constraints) - Techniques for specifying behavioral/executable semantics - Generative approaches (incl. code synthesis, compilation) - Meta-languages, meta-tools, language workbenches - AI-assisted language design and optimisation * Software Language Quality - Verification and formal methods for languages - Testing techniques for languages - Simulation techniques for languages - Model-based testing - AI-assisted validation * Software Language Integration and Composition - Coordination of heterogeneous languages and tools - Mappings between languages (incl. transformation languages) - Traceability between languages - Deployment of languages to different platforms - (AI-assisted) Language refactorings * Software Language Maintenance - Software language reuse - Language evolution - Language families and variability, language and software product lines * Domain-specific approaches for any aspects of SLE (design, implementation, validation, maintenance) * Empirical evaluation and experience reports of language engineering tools - User studies evaluating usability - Performance benchmarks - Industrial applications * Synergies between Language Engineering and emerging/promising research areas - Generative AI in language engineering (e.g., AI-based language modelling, AI-driven code generation tools) - Language engineering for AI. AI and ML language engineering (e.g., ML compiler testing, code classification, DSLs for AI processes and tasks…) - Quantum language engineering (e.g., language design for quantum machines) - Language engineering for physical systems (e.g., CPS, IoT, digital twins) - Socio-technical systems and language engineering (e.g., language evolution to adapt to social requirements) --------------------------- Types of Submissions --------------------------- SLE accepts the following types of papers: * Research papers: These are “traditional” papers detailing research contributions to SLE. Papers may range from 6 to 12 pages in length and may optionally include 2 further pages of bibliography/appendices. Papers will be reviewed with an understanding that some results do not need 12 full pages and may be fully described in fewer pages. * New ideas/vision papers: These papers may describe new, unconventional software language engineering research positions or approaches that depart from standard practice. They can describe well-defined research ideas that are at an early stage of investigation. They could also provide new evidence to challenge common wisdom, present new unifying theories about existing SLE research that provides novel insight or that can lead to the development of new technologies or approaches, or apply SLE technology to radically new application areas. New ideas/vision papers must not exceed 5 pages and may optionally include 1 further page of bibliography/appendices. * SLE Body of Knowledge: The SLE Body of Knowledge (SLEBoK) is a community-wide effort to provide a unique and comprehensive description of the concepts, best practices, tools, and methods developed by the SLE community. In this respect, the SLE conference will accept surveys, essays, open challenges, empirical observations, and case study papers on the SLE topics. These can focus on, but are not limited to, methods, techniques, best practices, and teaching approaches. Papers in this category can have up to 20 pages, including bibliography/appendices. * Tool papers: These papers focus on the tooling aspects often forgotten or neglected in research papers. A good tool paper focuses on practical insights that will likely be useful to other implementers or users in the future. Any of the SLE topics of interest are appropriate areas for tool papers. Submissions must not exceed 5 pages and may optionally include 1 further page of bibliography/appendices. They may optionally include an appendix with a demo outline/screenshots and/or a short video/screencast illustrating the tool. **Workshops**: Workshops will be organised by STAF. Please inform us and contact STAF 2026 organisers if you would like to organise a workshop of interest to the SLE audience. Information on how to submit workshops can be found on the STAF 2026 Website. --------------------------- Submission --------------------------- SLE 2026 has a single submission round for papers, including a mandatory abstract registration. Authors of accepted research papers will be invited to submit artefacts. --------------------------- Format --------------------------- Submissions have to use the ACM SIGPLAN Conference Format “acmart” ( https://sigplan.org/Resources/Author/#acmart-format) please make sure that you always use the latest ACM SIGPLAN acmart LaTeX template, and that the document class definition is \documentclass[sigplan,anonymous,review]{acmart}. Do not make any changes to this format! Ensure that your submission is legible when printed on a black and white printer. In particular, please check that colours remain distinct and font sizes in figures and tables are legible. To increase fairness in reviewing, a double-blind review process has become standard across SIGPLAN conferences. Accordingly, SLE will follow the double-blind process. Author names and institutions must be omitted from submitted papers, and references to the authors’ own related work should be in the third person. No other changes are necessary, and authors will not be penalized if reviewers are able to infer their identities in implicit ways. All submissions must be in PDF format. You can access the submission site from the conference website: https://conf.researchr.org/home/sle-2026 --------------------------- Concurrent Submissions --------------------------- Papers must describe unpublished work that is not currently submitted for publication elsewhere as described by SIGPLAN’s Republication Policy ( https://www.sigplan.org/Resources/Policies/Republication/) Submitters should also be aware of ACM’s Policy and Procedures on Plagiarism ( https://www.acm.org/publications/policies/plagiarism-overview) Submissions that violate these policies will be desk-rejected. --------------------------- Policy on Human Participant and Subject Research --------------------------- Authors conducting research involving human participants and subjects must ensure that their research complies with their local governing laws and regulations and the ACM’s general principles, as stated in the ACM’s Publications Policy on Research Involving Human Participants and Subjects ( https://www.acm.org/publications/policies/research-involving-human-particip…) If submissions are found to be violating this policy, they will be rejected. --------------------------- Reviewing Process --------------------------- All submitted papers will be reviewed by at least three members of the program committee. Research papers and tool papers will be evaluated concerning soundness, relevance, novelty, presentation, validation, and replicability. New ideas/vision papers will be evaluated primarily concerning soundness, relevance, novelty, and presentation. Tool papers will be evaluated concerning relevance, presentation, and replicability. For fairness reasons, all submitted papers must conform to the above instructions. Submissions that violate these instructions may be rejected without review at the discretion of the PC chairs. --------------------------- Artefact Evaluation --------------------------- SLE will use an evaluation process to assess the quality of artefacts on which papers are based to foster the culture of experimental reproducibility. Authors of accepted research papers are invited to submit artefacts. --------------------------- 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 2016 paper with the greatest impact, as judged by the SLE Steering Committee. --------------------------- Publication --------------------------- All accepted papers will be published in the ACM Digital Library. **AUTHORS TAKE NOTE**: The official publication date is the date the proceedings are made available in the ACM Digital Library. This date may be up to two weeks prior to the first day of the conference. The official publication date affects the deadline for any patent filings related to published work. --------------------------- Organisation --------------------------- * General chair: Arnaud Blouin, Univ Rennes, INSA Rennes, Inria, CNRS, IRISA * PC co-chair: Jordi Cabot, Luxembourg Institute of Science and Technology * PC co-chair: Shigeru Chiba, University of Tokyo, Japan --------------------------- Contact --------------------------- For additional information, clarification, or answers to any questions, please get in touch with the program co-chairs (jordi.cabot(a)list.lu and chiba(a)g.ecc.u-tokyo.ac.jp)

Nov. 20, 2025

UKSTUG Meeting: Norbert Hartl - Soil: a database for fun and profit - 26 November 2025

by UK Smalltalk

Soil ( https://github.com/ApptiveGrid/Soil ) is an object oriented database implemented completely in smalltalk/pharo. It makes it easy to build a persistent solution without the burden of mapping everything to some external DSL/database. It supports storing arbitrary graphs and enables transparent access to them. It has binary search indexes to make lookups of huge collections quite efficient. It is the main database behind ApptiveGrid - low code tool to build business processes. ( https://www.apptivegrid.de/) Norbert Hartl ( https://github.com/noha ) is an experienced software engineer and entrepreneur with a strong track record of delivering business projects and developing key libraries and frameworks. As the co-founder of ApptiveGrid and PharoPro, he focuses on creating efficient, zero-dependency software solutions that drive business innovation and streamline operations. This will be an online meeting. If you'd like to join us, please sign up in advance on the meeting's Meetup page ( https://www.meetup.com/ukstug/events/311265917/ ) to receive the meeting details.

Nov. 19, 2025

DevEx survey

by stephane ducasse

Hello people Sorry this is survey in french for developers, but it can interest french speaking developers. Bonjour, Pas plus de 5 min de votre temps! Je me permets de vous contacter afin de vous proposer de mener, au sein de vos équipes, une réplication de l’étude DevEx in Action, conduite en 2024 par N. Forsgren (Microsoft Research), E. Kalliamvakou (Github Next), A. Noda (DX), M. Greiler (DX), E. Houck (Microsoft) et M.-A. Storey (Université de Victoria). Article original disponible à https://queue.acm.org/detail.cfm?id=3639443 Cette réplication s’inscrit dans le cadre de ma thèse portant sur l’impact réciproque de la dette technique sur la santé mentale des développeurs. L’objectif de cette étude est d’évaluer l’expérience développeur (DevEx), qui définit la qualité de l’expérience vécue par les développeurs et développeuses dans leur environnement technique et organisationnel. L’étude s’appuie sur trois dimensions principales : les boucles de retour (feedback), la charge cognitive et la capacité à maintenir sa concentration. La réplication consiste à mesurer ces dimensions et leur impact sur les résultats perçus au niveau individuel, de l’équipe et de l’entreprise. Le dispositif repose sur un questionnaire unique et identique à celui de l’étude originale. Il est anonyme, volontaire et prend environ 5 minutes à remplir. Les réponses sont analysées par modélisation PLS-SEM (via SmartPLS 4), comme précisé dans l’étude originale. Lien du questionnaire : https://annac.limesurvey.net/422315?lang=fr Cordialement, Anna Cathelineau anna.cathelineau(a)gmail.com <mailto:anna.cathelineau@gmail.com>

Nov. 14, 2025

MPLR 2026 Call for Papers

by stephane ducasse

Dear Smalltalk friends Please find the following conference call for papers that can interest you. If you know other forums that could be interested in virtual machines, compilers …. do not hesitate to forward this call. S. Ducasse and C. Scholliers PC chair of MPLR 26 ################################################################################## The 23rd International Conference on Managed Programming Languages & Runtimes (MPLR, formerly ManLang, originally PPPJ) is a premier forum for presenting and discussing novel results in all aspects of managed programming languages and runtime systems, which serve as building blocks for some of the most important computing systems in use, ranging from small-scale (embedded and real-time systems) to large-scale (cloud-computing and big-data platforms) and anything in between (desktop, mobile, IoT, and wearable applications). https://2026.ecoop.org/home/mplr-2026 Important Dates --------------- - Abstract Submission Deadline: February 27, 2026 - Paper Submission Deadline: March 6, 2026 - Paper Author Notification: April 15, 2026 - Camera Ready for Papers: April 30, 2026 - Conference Date: June 29, 2026 All deadlines are 23:59 AoE (UTC-12h). #### Topics The areas of interest related to managed programming languages and runtime systems include but are not limited to: - **Virtual Machines** - Portable intermediate representations (e.g., JVM, WebAssembly, RPython, ...) - Managed runtime systems (e.g., GraalVM, Android Runtime (ART), V8, JavaScriptCore, .NET, …) - VM design and optimization - VMs for mobile and embedded devices - VMs for real-time applications - Memory management and garbage collection - Hardware/software co-design - Domain-specific languages - Security and privacy - Persistence - **Languages and Compilers** - Managed languages - Compilers and interpreters - Type systems and program logics - Language interoperability - Parallelism, distribution, and concurrency - **Techniques, Tools, and Applications** - Static and dynamic program analysis - Testing and debugging - Simulation - Refactorings - Program synthesis - Performance analysis and monitoring - Compiler and program verification and model checking If you are unsure whether a particular topic falls within the scope of MPLR ’26 or if you have any other questions, please do not hesitate to contact the Program Chair. #### Submission Categories MPLR accepts three types of submissions: - **Regular research papers**, describing novel contributions involving managed language platforms. Research papers will be evaluated based on their relevance, novelty, technical rigor, and contribution to the state-of-the-art. (Format: up to 12 pages, excluding bibliography and appendix); - **Work-in-progress research papers**, describing hot topics or promising new ideas, with perhaps less maturity than full papers. Work-in-progress papers will be evaluated with an emphasis on novelty and the potential of the new ideas instead of technical rigor and experimental results. (Format: up to 6 pages, excluding bibliography and appendix); - **Industry and tool papers**, presenting technical challenges and solutions for managed language platforms in the context of deployed applications and systems. Industry and tool papers will be evaluated on their relevance, usefulness, and results. Suitability for demonstration and availability will also be considered for tool papers. (Format: up to 6 pages, excluding bibliography and appendix; up to 12 pages allowed if justified by the content); Accepted submissions will be published in the ACM Digital Library, except if the authors prefer not to be included. MPLR 2026 submissions must conform to the ACM Policy on Prior Publication and Simultaneous Submissions and to the SIGPLAN Republication Policy. See http://www.sigplan.org/Resources/Policies/Republication #### Author Instructions Submissions need to use the ACM SIGPLAN format with the `sigplan` style. If you are using LaTeX, submissions need to use the `acmart` document class with the `sigplan` option (*not* the `sigconf` option). In the `acmart-primary.zip` file that downloads from the LaTeX (Version 1.90) link on the https://www.acm.org/publications/proceedings-template page, look for `samples/sample-sigplan.tex` as a guide. If you use Overleaf, be sure to change the `documentclass` option `manuscript` to `sigplan`. For ease of reviewing, please include page numbers in your submission using the LaTeX command `\settopmatter{printfolios=true}`. Please use the standard setting, e.g., the default font size for the SIGPLAN style is 10 point and the format uses two columns for the test. All submissions need to be in PDF format. MPLR now uses **double-blind reviewing**. **Authors should not show their names on a submission and should refer to their own work in third person.** We further recommend that they avoid publicizing the work, at least under the same or similar title, while it is under review. Please also ensure that your submission is legible when printed on a black and white printer. In particular, please check that colors remain distinct and font sizes are legible. Submission Site: https://mplr26.hotcrp.com

Nov. 13, 2025

Re: A thought for Vanessa Freudenberg

by Graham McLeod

Hi I would like to add my condolences and acknowledge her contribution over decades. First encountered her in the early 2000’s working on the Squeak plugin which allowed us to create a graphical modeller in the primitive browsers of the time. She faced many personal challenges in her life, but remained true to herself and faithful to Smalltalk. Go well my friend. KR Graham McLeod Owner/Chief Architect “Building Desirable Futures” Training • Consulting • Tools • Research graham(a)inspired.org <mailto:graham@inspired.org> https://www.inspired.org <https://www.inspired.org/>. landline: +27 21 531 5404 LinkedIn: https://www.linkedin.com/in/grahamatinspired/ > On 30 Oct 2025, at 11:14, stephane ducasse via Esug-list <esug-list(a)lists.esug.org> wrote: > > Hello Pharoers > > Today I just learned that Vanessa Freudenberg passed away. > And I’m super sad. I knew her from Squeak Central, Impara and the funny Plop Project. > Vanessa pushed SqueakJS and more projects. > At ESUG this year we had fun with the new version of Plop. > > I do not have contact with her family and friend but I want to express my sincere condolences. > Please pass them this message if you get in touch with them. > > S. > _______________________________________________ > Esug-list mailing list -- esug-list(a)lists.esug.org > To unsubscribe send an email to esug-list-leave(a)lists.esug.org

Oct. 30, 2025

A thought for Vanessa Freudenberg

by stephane ducasse

Hello Pharoers Today I just learned that Vanessa Freudenberg passed away. And I’m super sad. I knew her from Squeak Central, Impara and the funny Plop Project. Vanessa pushed SqueakJS and more projects. At ESUG this year we had fun with the new version of Plop. I do not have contact with her family and friend but I want to express my sincere condolences. Please pass them this message if you get in touch with them. S.

Oct. 30, 2025