![P11 possible points [Language]
• Ephemerons
• Using them in the image
• Replacing Weak / Finalization mechanisms
• Concurrency
• Cleaning up the concurrency mechanisms we have.
• Make the image to use higher level mechanisms.
27](https://image.slidesharecdn.com/01-2022-esug-pharo10-220923100139-11d0f308/85/Pharo-10-and-beyond-27-320.jpg)
![P11 possible points [Compiler]
• Clean Blocks
• Sharing them
• Full tool support
• Compiler Improvements
• New Optimizations
• Better Plugin support
• ...
28](https://image.slidesharecdn.com/01-2022-esug-pharo10-220923100139-11d0f308/85/Pharo-10-and-beyond-28-320.jpg)
![P11 possible points [UI]
• Multi Windows
• HDPI
• Bloc in preview
• Spec Backend
• Performance
29](https://image.slidesharecdn.com/01-2022-esug-pharo10-220923100139-11d0f308/85/Pharo-10-and-beyond-29-320.jpg)
![P11 possible points [Modularity]
• Pakbot
• Dependency management
• Projects
• Modularization
• Minimal Images
• External Projects
• Better Baselines
30](https://image.slidesharecdn.com/01-2022-esug-pharo10-220923100139-11d0f308/85/Pharo-10-and-beyond-30-320.jpg)
Pharo 10 and beyond
- 1. ESUG 2022 Pharo 10 and beyond S. Ducasse consortium-adm@pharo.org
- 2. Remember Pharo 90! • Full redesign of the Spec UI framework (new logic, application, style, GTK back-end) • NewTools: new playground, new inspector, new debugger (new error infrastructure and emergency debugger) • New composable completion framework • General speed up • Compiler optimisations 2
- 3. Remember Pharo 90! • Better Refactorings • Better parser for error recognition • Comments in Microdown format (Markdown compatible) • Fast universal FFI (Foreign Function Interface) • Idle VM + SDL20 and back-end (extended event handling, including trackpad support) • ARM 64 bits • Full block closures 3
- 5. Many Bugs Fixed & Improvements • + 1560 Pull requests • + 1100 Issues closed • 85 Di ff erent contributors 5
- 6. Many Bugs Fixed & Improvements 6
- 7. • Improving the development process • Shorter iteration to release • Reduced set of objectives • Better “Ready” de fi nition • Cut the fat 7 (After a large introspection…) We wanted a SMALLER Iteration
- 9. A side joke “it is better, it has less classes” said the lame OOP developer 9
- 10. Just smaller is trivial • Removing code by removing functionalities is easy • But we want same behavior and less code! 10
- 11. The real challenges Cleaning and consolidating existing functionalities Supporting users (deprecation) are more challenging and interesting! 11
- 12. •10% code reduction! •Having one good instead of three average versions •- 48 K LOC 12 Pharo10 a.k.a. Cut the FAT
- 13. 13 Removed old/duplicated code • Old Tools • V3 Compiler Support • Old Blocks & Bytecode • VM based event handling • Glamour / GTTools • Spec1
- 14. Spec 2: Main Elements • Now core is stable! • Core & Basic Layouts • Basic Presenters • Application Support • Styles / Themes • Code Presenter 14
- 15. • Di ff erent layouts and composition • Extended support for dynamic layouts • New dialog building • Transmissions • Direct support for Roassal & Cairo • Multiple backends (GTK / Morphic) • Spec Tests and Testing Support 15 Spec 2: Extended Features
- 16. • Migrating fi nal tools from Spec1 to Spec2 • Improving existing ones • Fixing issues and glitches • Improving Refactorings, Deprecator & Rewriting tools. • Improving Pro fi lers 16 Tooling
- 17. Fluid Class Syntax • Was sketched and presented in 2017 at ESUG • Took longer than we wanted but • Nice design • Scale well with multiple and optional parameters • Extensible • Clean and nice implementation • Is the default Pharo syntax! 17
- 19. Compiler Improvements • Unifying objects variables into a single hierarchy • Improved semantic analysis • Use Class and the Environment to lookup the variables • Use Variable hierarchy to model variables for name analysis • Improved AST Visitor • Pragma lookup speed-up • Compiler speed improvements 19
- 20. Refactorings • New Refactorings • Extract setUp method • Remove senders of method refactoring • Copy package as refactoring • Rename package (rename manifest) • Merge instance var x in y • Move to class side method • Create accessors with lazy initialization 20
- 21. Improved Refactorings • Deprecate method (simple version) • Deprecate class • Extract method refactoring • Replace senders by another • Rename vars in Traits, Convert temporary to instance variable • Push up method refactoring • Add access to pushUp and pushDown refactorings from source code • Permute parameters when add an argument • Abstract instance variable 21
- 22. Other Improvements • Sista Bytecodes w/ Full Block Closures • Memory management con fi guration • Integration with Windows • Zinc 22
- 23. • 3 Operating Systems (OSX / Linux / Windows) • 3 Architectures (ARM64 / ARM 32 / x86_64) • Full Linux Packages through OBS • Better FFI 23 Pharo 10: VM Improvements (2)
- 24. • Sockets • Clean up old code • GC Improvements • Logging • Stability, Speed • Updated Dependencies 24 Pharo 10: VM Improvements
- 26. Pharo 11’s possible points 26
- 27. P11 possible points [Language] • Ephemerons • Using them in the image • Replacing Weak / Finalization mechanisms • Concurrency • Cleaning up the concurrency mechanisms we have. • Make the image to use higher level mechanisms. 27
- 28. P11 possible points [Compiler] • Clean Blocks • Sharing them • Full tool support • Compiler Improvements • New Optimizations • Better Plugin support • ... 28
- 29. P11 possible points [UI] • Multi Windows • HDPI • Bloc in preview • Spec Backend • Performance 29
- 30. P11 possible points [Modularity] • Pakbot • Dependency management • Projects • Modularization • Minimal Images • External Projects • Better Baselines 30
- 31. Not optional P11 VM points :) • VM • Memory Management • PermSpace • New Image format • Meta-data • RISC-V 31