I totally appreciate the tone of this response — Smalltalk is such a simple language, and has such a rich class library, that the “sheer cliff” priciple comes into play. Smalltalk can be learnt in a a couple of days (I’ve trained many students) however, the incledible flexibility it offers, and the extensive class library can quickly lead to confusion early on. There’s no magic — your understanding of OOP and your creativity IS the limit.
Raspberry Pi is a very cool little chip (and so is C.H.I.P. for that matter) — both of which can be “controlled” by Smalltalk.
As an OO fan, and given the option, I’d choose Smalltalk for any new project, from massive multi-user mobile apps, through to embedded single purpose solutions.
Whatever language you choose, whatever platform you choose, there’s a learning curve. One advantage Smalltalk has over many other languages and operating systems, is that it performs in all roles, at all scales, typically without having to rewite and relearn.
“Serious” developers are all for this shit, however “populist” developers are are all about the so-called “cutting edge” which I’ve learnt means “suck it and see” things rather than actually getting things done… but I’m off on a rant :)
This was a tutorial on Smalltalk on Pi — and a great one. If you’re new to Pi, and new to Smalltalk, then you’re right — Richard cut to the chase. There are simpler tutorials out there for each that are probably better suited.
For me, is was perfect and I ordered my Pi to jump on the IoT bandwagon with Smalltalk as the catylist.