Download to read offline
Uploaded byPharo
Smalltalks13 pharo techoverview
This document discusses the vision and many planned changes for the Pharo programming environment. The vision is for Pharo to be clean, modern, innovative, and maintainable. It outlines numerous system cleanups, improvements to various tools and subsystems, and more fundamental changes like replacing the class organization, using ASTs and bytecode generation to improve performance, adding support for packages and object spaces. The goal is for Pharo to have an excellent user experience and be a collaborative environment for developers.
More Related Content
Similar to Smalltalks13 pharo techoverview
Smalltalks13 pharo techoverview
- 1.
- 2. Esteban Lorenzano Pharo “coreteam” since 1.5yr (and lots of other stuff before, but this is the cool part :)
- 3. Remember our vision • Clean • Modern • Innovative • Maintained,but not (necessarily) backward compatible
- 4. A “small” listof changes • System Cleanups • Morphic Cleanups • Widgets • Polymorph • Bootstrap • FileSystem • Announcements • Zinc/Zodiac • RPackage • Class organization • Command Line • Spec • Spec based tools • Class-Trait polymorphism • Fuel • Debugger/Inspector • Nautilus • Spec • VM Infrastructure • NativeBoost • VM including default plugins and libraries • Athens • UI Improvements • Keybindings • Metacello2 / Filetree • Zeroconf • Community available infrastructure • • • • Opal Class Layouts Slots Code Critics • Manifest • RB/AST • Refactors and more refactors • AST Smart Suggestions • …
- 5. “It is justa bunch of random changes.” It is not!
- 6. It is allabout evolution There is no such thing as “a small change”. Is through a stack of continuous changes that you create one that is revolutionary.
- 7. “If it ain’tbroke, don’t fix it.” Yeah… just that it does not always works!
- 8. It is allabout evolution! “Patch stacking techniques” work fine for a while, but at the end you have a poorly designed system.
- 9. Subsystem replacement • Not justfor the joy of change. - Enhance design. - Allow further development.
- 10. RPackage • First class objects - Replacementof PackageInfo (and System Categories) - Replacement also of Class Organizer
- 11. RPackage ✓ Better handling forpackages and classes ✓ We can now include metadata there • We can think on different/orthogonal ways of categorization
- 12.
- 13. Opal • Fully reified • Semantic analysis,IR translation, Byte code generation, each stage visiting the AST. • Marcus wants to use PetitParser :)
- 14. Opal ✓ Many “small optimizations” ✓ ClassLayouts/Slots • Reflectivity (allowing “details” like real breakpoints)
- 15. New debugger ✓ Fully reified ✓ Pluggableinspectors • Moldable debuggers
- 16. Object spaces • Experiment withother object formats • Ability to interact with other environments ✓ Image inspection & repair - Remote control (maybe with Seamless) - Dev environment vs. app environment
- 17. Native Boost • Dynamic codegeneration (ASMJIT) • Many applications ✓ FFI ✓ Athens - Mate - Move plugins/external code from C to Pharo
- 18. Athens • Better suited formodern screens • CPU usage improvements • Replace old BitBlt based morphs
- 19.
- 20. User eXperience It isnot enough to be the best environment around, we also need to look like the best environment around.
- 21. Brave new world Wewant to create a cool environment for all people interested in participate
- 22. “Ask not whatPharo can do for you, but what you can do for Pharo” (because it is yours)
- 23.
- 24. … a worldin which you modify and interact nicely (and in runtime) with the outside world.
- 25. … a worldwith contained sources and changes as transaction logs.
- 26. … a worldin which you can deploy other worlds, worlds that you can create by doing: ! Pharo new fork.
- 27. … or doing: ! Pharonew forkAt: 192.168.1.42
- 28.