Pharo is a pure object-oriented programming language and a powerful environment, focused on simplicity and immediate feedback (think IDE and OS rolled into one).
Pharo @ FOSDEM
Come to our stand to meet the community behind Pharo. Meet key engineers and researchers behind the language development. Meet the rich multiple communities that pharo hubs, from radically different origins.
From public research to private business, from software & language research & development to human rights hacktivism, Pharo community is a really rich meltingpot of international technological improvement, political struggle and beautiful human exchange!
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: The 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 contributing constantly with frameworks and libraries.
Fully open-source: Pharo full stack is released under MIT License and available on GitHub
You may join us on our different communications endpoints :)
Pharo language has two faces, the industrial face and the research face. This last year we have been brewing many new things.
Language/VM: We have extended the JIT Compiler, implemented a large battery of tests. Extend it to ARM64bits. We implemented a new system for threaded FFI calls, that allow us to have partial parallelism. We added new technologies on concurrent programming, that allow consistent definition of tasks and at some point binding with FFI threads if it is the case.
IDE: We are working on automated distributed testing for reduce the testing time of the projects, allowing the developers to quickly run tests on development. We have been developing bindings to GTK, and extending our own IDE to have multiple bindings (so far, GTK and Morphic -a native approach-). We are beta testing our new debugger, and inspecting tools for live programming development. Including replay, object specific debugging, and other state of the art features. We implemented a markdown subset parser and rendered for having the language comments written in markdown
Generated at 2022-12-02 10:30:18.050190223 +0000 UTC m=+0.074615904
This work is licensed under the Creative Commons Attribution 2.0 Belgium Licence.
To view a copy of this licence, visit http://creativecommons.org/licenses/by/2.0/be/deed.en
or send a letter to Creative Commons, 444 Castro Street, Suite 900, Mountain View, California,
All content such as talks and biographies is the sole responsibility of the speaker.