- Pharo-dev - lists.pharo.org

Info required for bootstrapping pharo on GNU Guix
by Nicolas Graves May 21, 2024

May 21, 2024

Hi Pharo community, I'm trying to package pharo in the GNU Guix linux distribution. Since the distribution is focused on reproducibility and avoids using binary code when possible, for that I need to reproduce the bootstrapping steps that are embedded in Pharo. I understand from some developper online comment that this is possible. I've started to work on this and it seems feasible, at least I get the dependency loop, what I've some difficulty is to get precisely when it's possible to get started. ------------------- | v pharo VM pharo â§ | ------------------- If I'm correct, - bootstrapping is very clear after version ~7.0.0, and with a proper build, just follow the distribution numbers in wget's with a cmake build-system. - for earlier versions, there's the repository https://github.com/pharo-project/PharoBootstrap that seems (git history) to be able to go back to Pharo 30. - I understand that at some point, Squeak and Pharo used to have the same VM. I have access to a squeak-vm 4.10.2.2614 in Guix, and I've seen this is in Pharo's ftp files, so I guess I can start there. What I need: - Some indication about the first version of Pharo that I'm able to build purely from squeak-vm, and where to find its source code (git+version or commit if possible, I seem to only be able to find its binaries currently in phero's ftp files). - Any useful information for early bootstrap steps. Some useful information on my side: - During the build process in Guix, we can't download data, so the entire bootstrap chain has to be explicited at once, hence the need to go back to the beginning in this case. Thanks in advance! -- Best regards, Nicolas Graves

3 4

This week (20/2024) on the Pharo Issue Tracker
by Marcus Denker May 17, 2024

May 17, 2024

# Pharo 12 - Backport use of FormSet for ToggleMenuItemMorph submenu markers #16631 https://github.com/pharo-project/pharo/pull/16631 # Ehancements - [Enhancement] Add "copy class name" to extras menu in Calypse #16635 https://github.com/pharo-project/pharo/pull/16635 - Add missing RGGlobalVariable>>isInstanceVariable #16644 https://github.com/pharo-project/pharo/pull/16644 - Introduce CompiledMethod>>#isInstanceSide #16626 https://github.com/pharo-project/pharo/pull/16626 # Fixes - Issue 16430 - String>> asSymbol no protected against concurrent access (alternative solution) #16565 https://github.com/pharo-project/pharo/pull/16565 - [Bug]: Date>>#addMonths: should Respect Offset #16603 https://github.com/pharo-project/pharo/pull/16603 - sort subdirectories in the same order as the file tree table #748 https://github.com/pharo-spec/NewTools/pull/748 # VM - Fixed VirtualMachine 76 and 78 parameters #16641 https://github.com/pharo-project/pharo/pull/16641 - Do not retain any selectors in CogAbstractInstruction #798 https://github.com/pharo-project/pharo-vm/pull/798 - add tests for type harmonization #807 https://github.com/pharo-project/pharo-vm/pull/807 - remove warning because of type and unsigned shift issues #800 https://github.com/pharo-project/pharo-vm/pull/800 - Fixed ntb page selection change announcement if built without pages #1542 https://github.com/pharo-spec/Spec/pull/1542 # Package Structure - Sindarin/ScriptableDebugger should be listed as external project #16653 https://github.com/pharo-project/pharo/pull/16653 - Sindarin in Pharo13 need to be loaded from Pharo13 branch of ScriptableDebugger (and not Pharo12 branch) #751 https://github.com/pharo-spec/NewTools/pull/751 - Simplify Calypso packaging #16602 https://github.com/pharo-project/pharo/pull/16602 - Cleanup: CoverageCollectorTest should be in an own test package #16613 https://github.com/pharo-project/pharo/pull/16613 # Rules - proposition rule for nil branch #16547 https://github.com/pharo-project/pharo/pull/16547 - [Enhancement] Add a rule ReBaselineProperlyPackagedRule #16630 https://github.com/pharo-project/pharo/pull/16630 - [Enhancement] Add a rule ReBaselineWithProperSuperclassRule #16633 https://github.com/pharo-project/pharo/pull/16633 - proposition for a potential new rule: useless ifTrue:ifFalse: #16638 https://github.com/pharo-project/pharo/pull/16638 - add ReStatementsAfterReturnConditionalRule #16640 https://github.com/pharo-project/pharo/pull/16640 - Review ReClassNotCategorizedRuleTest>>#testRule #16649 https://github.com/pharo-project/pharo/pull/16649 - Improve ReBaselineProperlyPackagedRule and ReBaselineWithProperSuperclassRule and cover with tests #16648 https://github.com/pharo-project/pharo/pull/16648 - Enhancement: Provide a lint rule to check for a "super initialize" call in instance side #initialize methods #16615 https://github.com/pharo-project/pharo/pull/16615 - tests for rules from the General-Rules package #16474 https://github.com/pharo-project/pharo/pull/16474 # Cleanups - Reduce references to Undeclared global variable #16642 https://github.com/pharo-project/pharo/pull/16642 - Remove deprecated way to access the global package organizer #754 https://github.com/pharo-spec/NewTools/pull/754 - Remove the package Deprecated12, introduce package Deprecated13 #16538 https://github.com/pharo-project/pharo/pull/16538 - proposition refactoring -> Cleanup: 2 duplicated methods in FreeType #16583 https://github.com/pharo-project/pharo/pull/16583 - Clean up in SDL_Texture and SDL_Renderer #16601 https://github.com/pharo-project/pharo/pull/16601 - Simplify script pragma for FinderUI #16623 https://github.com/pharo-project/pharo/pull/16623 - CommentTestCase should be moved to PharoDocComment-Tests #16619 https://github.com/pharo-project/pharo/pull/16619 - Package "System-DependenciesTests" should be "System-Dependencies-Tests" #16621 https://github.com/pharo-project/pharo/pull/16621 - Cleanup: AthensTransformTest>>transformClass should be in accessing #16628 https://github.com/pharo-project/pharo/pull/16628 - Fix lint in ReShouldSendSuperSetUpAsFirstMessage class>>#checksMethod (second PR) #16643 https://github.com/pharo-project/pharo/pull/16643 - Remove part of ReAsClassRule about #asClass #16658 https://github.com/pharo-project/pharo/pull/16658 - Cleanup: Remove deprecated announcement #SnapshotDone in SnapshotOperation>>#performSnapshot for Pharo 13 #16657 https://github.com/pharo-project/pharo/pull/16657 - Cleanup: unnecessary class BlLoadProjectWorldMenu #16655 https://github.com/pharo-project/pharo/pull/16655 - SourceFile>>#isOpen should use isNotNil #16651 https://github.com/pharo-project/pharo/pull/16651 - Remove Gofer #16606 https://github.com/pharo-project/pharo/pull/16606 - Remove reference to a deprecated class #1822 https://github.com/pharo-vcs/iceberg/pull/1822 - Fixing call to deprecated code #749 https://github.com/pharo-spec/NewTools/pull/749 - Use isNotNil instead notNil in initializePresenters #753 https://github.com/pharo-spec/NewTools/pull/753 # Website - Update community.md: Social Media Section #74 https://github.com/pharo-project/pharo-website/pull/74 - Update community.md: update tweet suggestion form #73 https://github.com/pharo-project/pharo-website/pull/73 - Update Companies.md #72 https://github.com/pharo-project/pharo-website/pull/72 - Update 2024-04-26-pharo12-released.md: fix typy #69 https://github.com/pharo-project/pharo-website/pull/69

1 0

IWST Deadline Extension
by Guille Polito May 17, 2024

May 17, 2024

Dear Community, Please let us inform you that the submission deadline for the full/short papers has been extended until May 31st, 2024 AoE. Let us remind you of the submission details: - Short position papers (5 to 10 pages) describing fresh ideas and early results. - Full papers (more than 10 pages) with deeper descriptions of experiments and research results. Please also consider that you may submit another work other than your original abstract. Paper accepted for publishing will be published within a *CEUR-WS Proceedings>https://ceur-ws.org/*. Hence, both submissions and final papers must be prepared using the *CEUR ART style>https://ceur-ws.org/Vol-XXX/CEURART.zip*. We recommend using the template in single-column style, although you may use two columns. CEUR proceedings accept papers in both styles as soon as they follow the template and have 5 or more pages. The IWST team, Gordana, Guille, and Steven https://esug.org/2024-Conference/IWST2024.html

1 0

[Website] updated forms to suggest companies and news entries
by Marcus Denker May 16, 2024

May 16, 2024

Hi, I have updated two forms ob pharo.org 1) Companies using Pharo https://www.pharo.org/Companies 2) Suggest news https://www.pharo.org/community see the link in the Social Media section The forms for now have simple workflows attached to send emails to do the next step manually. Marcus

1 0

Open Call: Object-Centric Breakpoints experiment
by Steven Costiou May 14, 2024

May 14, 2024

Dear Community, as part of a research project in the EVREF team, we are looking for people to participate to an empirical experiment on object-centric breakpoints - a debugging tool present in Pharo 9. Many people from the community already participated, and we thank them very much ð We are still looking for participants, we need 40 people to do the experiment! Please help us, in return it helps us understand better our tools and their impact and therefore build better tools for the Pharo community! For those who want to know a bit more, see my original email below. For those who just want to jump at the experiment, you can go there https://github.com/Pharo-XP-Tools/XPImageGeneration/tree/exp-ocd Thanks in advance ð Steven. --- We would like to invite you to participate to our experimental study on Object-Centric Breakpoints. This study aims to evaluate and to understand how Object-Centric Breakpoints impacts the debugging activity. This experiment takes place in **Pharo 9**. In this experiment, we ask you to solve 2 debugging tasks, one with standard Pharo tools and one other with Object-Centric Breakpoints. Between the two tasks, you will have to follow a tutorialand warmup tasks to learn how to use the tool. **How to Participate:** All instructions are here, please read them carefully: https://github.com/Pharo-XP-Tools/XPImageGeneration/tree/exp-ocd **About the Experiment:** The experiment last between 40 minutes and 2 hours. Participants should have experience with Pharo development and debugging. We recommend having more than 6 months experience in Pharo and debugging in general. You will gain insights into the Object-Centric Breakpoints approach and contribute to advancements in debugging research. Help us to build better debugging tools that help you debug! **Some constraints:** - You are not allowed to load external tools and baselines, but you can use anything that is in the base image - Please do the experiment in one shot if possible without interruptions - The experiment sends anonymous data to our inria server, please make sure that you have a valid internet connection - Please try to use the object-centric breakpoints when the experimental framework asks you to **Notes:** Participation is voluntary, and everything is anonymous. You can abandon the experiment at any point (and your data will be discarded). For any question, you can contact us: steven.costiou(a)inria.fr and valentin.bourcier(a)inria.fr Thank you for considering participating in our study. Your contribution will be valuable in advancing the field of debugging and helping us understand what tools we need to build for Pharo. Sincerely, Steven and Valentin, EVREF team, Inria

1 1

This week (19/2024) on the Pharo Issue Tracker
by Marcus Denker May 14, 2024

May 14, 2024

# Pharo 12 - 16576-Problem-with-completion-in-the-tutorial #16582 https://github.com/pharo-project/pharo/pull/16582 # Virtual Machine - Bump to MacOS 11 and above #792 https://github.com/pharo-project/pharo-vm/pull/792 - Do not use asserta: in a statement #788 https://github.com/pharo-project/pharo-vm/pull/788 - Moving pharo.signatures files for OSX Bundle to Resources folder #770 https://github.com/pharo-project/pharo-vm/pull/770 # Features - New debugger extension model to display dynamic extensions #739 https://github.com/pharo-spec/NewTools/pull/739 - add asAccessor #16579 https://github.com/pharo-project/pharo/pull/16579 - Make it easier to diagnose mock failures by printing message sends properly and storing the send history in the mock #16555 https://github.com/pharo-project/pharo/pull/16555 - add two's complement display for negative integers #746 https://github.com/pharo-spec/NewTools/pull/746 # Fixes - Make ToggleMenuItemMorph use a FormSet for the submenu marker #16510 https://github.com/pharo-project/pharo/pull/16510 - Taskbar option to close windows hidden behind other windows #16552 https://github.com/pharo-project/pharo/pull/16552 - prof stef lesson view did not understand has binding of #16578 https://github.com/pharo-project/pharo/pull/16578 - fix precedence computation #16581 https://github.com/pharo-project/pharo/pull/16581 # Refactoring Engine - Fix RBCompositeRefactoryChange>>#defineClass: argument name #16600 https://github.com/pharo-project/pharo/pull/16600 - Refactor: preconditions return array of preconditions by default #16527 https://github.com/pharo-project/pharo/pull/16527 # Rules - add ReOverridingExtentsionMethod rule #16550 https://github.com/pharo-project/pharo/pull/16550 - add rule to avoid that TestCase rely on Initialize #16513 https://github.com/pharo-project/pharo/pull/16513 # Tests (Green tests on CI) - Fix testCodeCruftLeftInMethods #16598 https://github.com/pharo-project/pharo/pull/16598 - Update roassal to v1.06d #16595 https://github.com/pharo-project/pharo/pull/16595 - Fixing reflectivity tests that can randomly fail because of unstable and unpredictable tests generating methods #16584 https://github.com/pharo-project/pharo/pull/16584 - 16569-CI-Pharo13-code-with-halt-was-merged #16570 https://github.com/pharo-project/pharo/pull/16570 - clearing debugger subscriptions and subcomponents in StDebuggerExtensionMechanismTest>>#tearDown #712 https://github.com/pharo-spec/NewTools/pull/712 # Cleanups - Renaming DebugPointSideEffect into DebugPointMetaBehavior #16563 https://github.com/pharo-project/pharo/pull/16563 - Cleanup: TestCase class>>#lastRunMethodNamed: #16588 https://github.com/pharo-project/pharo/pull/16588 - Cleanup: TestCase class>>#hasErrorTest, TestCase class>>#hasPassedTest and TestCase class>>#hasFailedTest #16586 https://github.com/pharo-project/pharo/pull/16586 - Changed 'Transcript show:' construct to 'self trace' #16385 https://github.com/pharo-project/pharo/pull/16385 - removing dependency to UIManager in StFuelStackCommand #745 https://github.com/pharo-spec/NewTools/pull/745 # Documentation - Update CONTRIBUTING.md #16575 https://github.com/pharo-project/pharo/pull/16575

2 3

IWST Paper Submission Deadline is Approaching!
by Guillermo Polito May 13, 2024

May 13, 2024

Dear community, IWST invites everybody to submit full/short papers to be considered to be plublished in the IWST 2024 Proceedings. Papers can both be presented in the conference's IWST track and appear in proceedings independently of the initially submitted abstracts. Full/short paper submission deadline: May 19th, 2024 We are looking for papers of two kinds: - Short position papers (5 to 10 pages) describing fresh ideas and early results. - Full papers (more than 10 pages) with deeper description of experiments and of research results. Paper accepted for publishing will be published within a *CEUR-WS Proceedings>https://ceur-ws.org/*. Hence, both submissions and final papers must be prepared using the *CEUR ART style>https://ceur-ws.org/Vol-XXX/CEURART.zip*. We recommend to use the template in single column style, although you may use two colums. CEUR proceedings accepts papers in boths styles as soon as they follow the template and have 5 or more pages. The IWST team, Gordana, Guille and Steven https://esug.org/2024-Conference/IWST2024.html

3 3

Re: [Esug-list] [ANN] Soil release v1
by Norbert Hartl May 8, 2024

May 8, 2024

> Am 06.05.2024 um 16:47 schrieb Dirk Nel <dirkockertnel(a)gmail.com>: > > I'll definitely check it out..! and for those who are not in the know... what inspired the name? :) - I like the word - It has only four letters which qualifies as a class prefix - To me as a non-native speaker it means: ground layer you can build/grow on Norbert > > On Wed, 24 Apr 2024 at 17:47, Tim Mackinnon <tim(a)testit.works> wrote: >> That's really exciting news... appreciate you sharing it with the wider community (I know when you mentioned its existence a while back I went and watched the Esug recordings to get more info, and looked at some of the extensive test cases to get a feel on what it looked like - its neat). >> >> Having multiple options for persisting data (from simple Fuel up to Soil and Glorp and Gemstone) is very useful. >> >> Tim >> >> On Wed, 24 Apr 2024, at 12:52 PM, Norbert Hartl wrote: >>> ...we said at last ESUG that there will be a release soonish but as usual it doesn't go that fast. >>> >>> But now we are very happy to announce that Soil has a first public release v1. So what is soil? >>> >>> Soil is an object oriented database in pharo <http://pharo.org/>. It is transaction based having ACID transactions. It has binary search capabilities with SkipList and BTree+ indexes. It aims to be a simple yet powerful database making it easy to develop with, easy to debug with, easy to inspect, ... >>> >>> More details at https://github.com/ApptiveGrid/Soil >>> >>> This release is still considered early stage because >>> >>> although in ApptiveGrid there are over 4000 instances of it and there are other users there isn't a wider range of use cases, yet. So it is not fully battle tested. This just as reminder when you start compaining I need somewhere to point my finger to and say "I told you!" ;) >>> there are few things missing that you might expect like garbage collection, etc. >>> >>> So but it is definetely usable and awaiting the brave ones of you to try. >>> >>> Hopy you enjoy it! >>> >>> Norbert & Marcus >>> _______________________________________________ >>> Esug-list mailing list -- esug-list(a)lists.esug.org <mailto:esug-list@lists.esug.org> >>> To unsubscribe send an email to esug-list-leave(a)lists.esug.org <mailto:esug-list-leave@lists.esug.org> >>> >> >> _______________________________________________ >> Esug-list mailing list -- esug-list(a)lists.esug.org <mailto:esug-list@lists.esug.org> >> To unsubscribe send an email to esug-list-leave(a)lists.esug.org <mailto:esug-list-leave@lists.esug.org>

3 5

Re: [Pharo-users] Re: [Esug-list] Re: [ANN] Soil release v1
by Sabine M May 8, 2024

May 8, 2024

I am always thinking of this movie when hearing âSoilâ. Googling for it now, I see that it has another spelling. https://en.wikipedia.org/wiki/Soylent_Green Gesendet von Outlook fÃ¼r iOS<https://aka.ms/o0ukef> ________________________________ Von: Cody Sevier <sevierit(a)gmail.com> Gesendet: Wednesday, May 8, 2024 5:43:24 PM An: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> Cc: Norbert Hartl <norbert(a)hartl.name>; Dirk Nel <dirkockertnel(a)gmail.com>; Pharo Dev <pharo-dev(a)lists.pharo.org>; Tetaz, Jean-Pierre via Esug-list <esug-list(a)lists.esug.org> Betreff: [Pharo-users] Re: [Esug-list] Re: [ANN] Soil release v1 Or soiling yourself, aka incontinence... Isn't English illogical fun! Cody On Wed, May 8, 2024, 10:41â¯AM Dale Henrichs <dale.henrichs(a)gemtalksystems.com<mailto:dale.henrichs@gemtalksystems.com>> wrote: To me as a non-native speaker it means: ground layer you can build/grow on Haha, Soil can also be thought of as "ground up stone" :) Dale On Wed, May 8, 2024 at 7:13â¯AM Norbert Hartl <norbert(a)hartl.name<mailto:norbert@hartl.name>> wrote: Am 06.05.2024 um 16:47 schrieb Dirk Nel <dirkockertnel(a)gmail.com<mailto:dirkockertnel@gmail.com>>: I'll definitely check it out..! and for those who are not in the know... what inspired the name? :) - I like the word - It has only four letters which qualifies as a class prefix - To me as a non-native speaker it means: ground layer you can build/grow on Norbert On Wed, 24 Apr 2024 at 17:47, Tim Mackinnon <tim(a)testit.works> wrote: That's really exciting news... appreciate you sharing it with the wider community (I know when you mentioned its existence a while back I went and watched the Esug recordings to get more info, and looked at some of the extensive test cases to get a feel on what it looked like - its neat). Having multiple options for persisting data (from simple Fuel up to Soil and Glorp and Gemstone) is very useful. Tim On Wed, 24 Apr 2024, at 12:52 PM, Norbert Hartl wrote: ...we said at last ESUG that there will be a release soonish but as usual it doesn't go that fast. But now we are very happy to announce that Soil has a first public release v1. So what is soil? Soil is an object oriented database in pharo<http://pharo.org/>. It is transaction based having ACID transactions. It has binary search capabilities with SkipList and BTree+ indexes. It aims to be a simple yet powerful database making it easy to develop with, easy to debug with, easy to inspect, ... More details at https://github.com/ApptiveGrid/Soil This release is still considered early stage because * although in ApptiveGrid there are over 4000 instances of it and there are other users there isn't a wider range of use cases, yet. So it is not fully battle tested. This just as reminder when you start compaining I need somewhere to point my finger to and say "I told you!" ;) * there are few things missing that you might expect like garbage collection, etc. So but it is definetely usable and awaiting the brave ones of you to try. Hopy you enjoy it! Norbert & Marcus _______________________________________________ Esug-list mailing list -- esug-list(a)lists.esug.org<mailto:esug-list@lists.esug.org> To unsubscribe send an email to esug-list-leave(a)lists.esug.org<mailto:esug-list-leave@lists.esug.org> _______________________________________________ Esug-list mailing list -- esug-list(a)lists.esug.org<mailto:esug-list@lists.esug.org> To unsubscribe send an email to esug-list-leave(a)lists.esug.org<mailto:esug-list-leave@lists.esug.org> _______________________________________________ Esug-list mailing list -- esug-list(a)lists.esug.org<mailto:esug-list@lists.esug.org> To unsubscribe send an email to esug-list-leave(a)lists.esug.org<mailto:esug-list-leave@lists.esug.org>

1 0

[ANN] Pharo 12 Release !
by Esteban Lorenzano May 8, 2024

May 8, 2024

Dear Pharo users and dynamic language lovers: We have released Pharo <https://pharo.org/> version 12! 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 complete list of changes and improvements is available in our Changelog <https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo120Chang…> Some highlights of this amazing version: Highlights New breakpoint system The debug point system is a breakpoint model that supersedes the previous implementation of breakpoints and watchpoints. They are configurable, composable, and extensible. The traditional breakpoints remain available, including conditional breakpoints, one-time breakpoints, and object-centric breakpoints. Additionally, there are new types of breakpoints, such as chained-breakpoints, which condition the activation of certain breakpoints on the triggering of others (e.g., breakpoint B only activates if breakpoint A is hit first). Debug points also feature a dedicated browser and integration options. Tools * Scalable fluid class syntax is now the default one * Preparing the introduction of the Bloc graphic system by migrating more tools to Spec2 widgets * Spec2 UI framework enhancements to support GTK 4 * Leaner version of the Metacello package manager * More robust and strict mode for FFI System * New architecture for refactorings and domain specific transformations * Code loading speed improvement * Fast browsing via fully optimized package tags * Optmized memory usage via optimized method protocols * Compiler simplifications and improvements Virtual machine * Massive image support with permanent space * String/ByteArray comparison speed up Development Effort This new version is the result of 1895 Pull Requests integrated just in the Pharo repository. We have closed 865 issues and received contributions from more than 70 different contributors. We have also a lot of work in the separate projects that are included in each Pharo release: * http://github.com/pharo-spec/NewTools <https://github.com/pharo-spec/NewTools> * http://github.com/pharo-spec/NewTools-DocumentBrowser <https://github.com/pharo-spec/NewTools-DocumentBrowser> * http://github.com/pharo-spec/Spec <https://github.com/pharo-spec/Spec> * http://github.com/pharo-vcs/Iceberg <https://github.com/pharo-vcs/Iceberg> * http://github.com/ObjectProfile/Roassal3 <https://github.com/ObjectProfile/Roassal3> * http://github.com/pillar-markup/Microdown <https://github.com/pillar-markup/Microdown> * http://github.com/pillar-markup/BeautifulComments <https://github.com/pillar-markup/BeautifulComments> * http://github.com/pharo-project/pharo-vm <https://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 12.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 <https://pharo.org/download> Learn Pharo: http://pharo.org/documentation <https://pharo.org/documentation>

9 9