Hi Richard, I had the same impression, that "Pharo is Smalltalk's successor". (Without any negative feelings toward VAST and VW; they fill a very important role for commercial use -- businesses depend on the kind of support that a commercial distribution provides and are very willing to fund that.)
The future of Smalltalk is being created every day with commits to the Pharo Project. Who's to say a company can't be created to provide commercial support for Pharo in the way that Red Hat does for Linux? And the Pharo Consortium is, in many ways, already one such entity. So please do contribute to making the booklets better, Richard! I started last fall (and need to start up again) and found it very fulfilling, as well as educational. It's easy to do; for you & others, here are the basic steps: 1. Fork a booklet repository and then clone it. 2. Set a git 'upstream' to the original (because you'll be trading revisions as you go). 3. Edit the Pillar markdown, add new material, etc. 4. Push and submit a Pull Request. 5. Continue working (i.e., start a 'pipeline' of edit submissions). 6. Note that you can modify the target of a PR while the PR is still "in review". 6. Check the WIP 'releases' that the CI system generates to proofread. I was using Atom and it's markdown rendering, which is imperfect, but it was sufficient. Sean DeNigris recently suggest editing in Gtoolkit's live Pillar editor: "It's beta, but a compelling experience. I did a little screencast here: https://youtu.be/GZOYF82h9qA";. I'm looking at it this week for my own use. There's also the 'Documentation' channel on the Pharo Discord site. I'd like to see the 'doc writers' start to interact there (and here); the last Discord entry was 6 weeks ago... -Ted -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
