From https://squeak.org you want to get an introduction. So you scroll down and there are PDF's that look like books. So you avoid them because you don't want to read a book. Then you click "More" where you go to: https://squeak.org/documentation/. On that page the options are:
The first "Terse Guide" sounded good to me but it is basically unreadable. I totally get why it exists but should it really be the first thing on this page? I skipped "Squeak Documentation" because it sounded like a language reference. I tried "Introductory Squeak" which is an archived page that is basically a wall-o-text and completely unreadable. "Squeak Language and Classes Reference": I am not looking for a reference, "Smalltalk: A White Paper Overview": definitely not looking for a white-paper, "Squeak in a Nutshell": an incomplete work in progress from 2006, "Morphic Framework": what is Morphic?.
I know squeak is a project with a long history and deep roots in academia. However for something that positions itself as being an intuative coding tool there is a massive WTF when you are coming at it from fresh. Those 7 items are the first thing your users will look at. They need to be super relevant, super easy, and super fast. Something like:
A single web page. No installation guide included - have as a separate link at the top: "To learn how to install squeak click here". No preliminary discussion about squeak, no philosophical BS - just stright into a short and sweet cut-n-paste tutorial with short and clear steps with screenshots. No discussions about hotkeys, debuggers, nothing.
The "browser" in squeak behaves strangely. Clicking in one of the top panes sometimes triggers a template to be pasted into the bottom box, sometimes not. It feels like the model is somehow broken.
GBdxebGmkxbX4GAM BK kz7kn7qYdpT74Hrc FB gJhs8zLVf83JgsTB FB