Dan Banay's #Smalltalk-80 "By the #Bluebook" implementation—tis a product of love!
SOFTWARE ENTRYPY:
#Smalltalk-80—236 classes
Cuis 7.0—675 classes
Squeak 6.0—2832 classes
Pharo 11.0—9986 classes
I miss those simpler days of #computing, back in the late 1970s and the early 1980s, when the #hardware #power was just high enough to do substantive work cheaply, and the #software #entropy was still low enough that one person could grasp almost any codebase in its entirety.
This post is over a decade old. Bu it looks from an original angle for viewing what Lisp and Smalltalk have in common and discover the same underlying idea. Recommended.
https://insearchofsecrets.com/2014/08/04/lisp-smalltalk-and-the-power-of-symmetry/
Hot take: your first three #programming languages should be #lua, then #clojure, then #smalltalk. Your production language should be your fourth language.
@screwtape @dougmerritt "Objective-C combines the expressive power of C with the speed & performance of Smalltalk." :)
ST is an incredibly powerful tool, but it's trapped in the GUI, and an outdated one, it's not really expressive in code itself. Its performance is so crippling. And you can't disentangle "a program" from the workbench, you ship the workbench to the client, which sucks ass.
Java and Objective-C got the good parts and you can make applications in them.
#smalltalk
@screwtape
However, the workaround, so that you need not wait an unbounded and unguessable amount of time, is to go to the post's home server.
(The post is about "I like all #programming languages but I have only a few that are my favourites. #Smalltalk is one of those few. But all the current open-source implementations still sport that Smalltalk-80, last-Century chic look....[back then Smalltalk] looked positively fresh, futuristic, and fun. But that look is now 45 years old." Etc.)
In the hopefully unlikely absence of still further errors, it should then be immediately readable -- although I believe *replying* to such a thing still results in that remote-to-you server telling your Mastodon client to take you back to your home server to make the reply.
I forget if I always have to actually follow the person who posted as an additional step in that reply.
I like all #programming languages but I have only a few that are my favourites. #Smalltalk is one of those few. But all the current open-source implementations still sport that Smalltalk-80, last-Century chic look.
I learned the language on the XEROX Smalltalk-80 system, so this look-and-feel holds that certain nostalgic charm for me. And when we were all using the VT100 terminal, Smalltalk's bitmap graphics and MVC GUI looked positively fresh, futuristic, and fun. But that look is now 45 years old. My goodness, let us just get over those garish colours and serif fonts, already!
These days, #Pharo's look-and-feel is perhaps the least offensive to the modern eye. But even it has that mouldy, cheesy look.
I am perfectly happy to use the classic Smalltalk-80 language in its original form; its design is ageless. But I find no technical, economical, practical, or aesthetic justifications for retaining that 1980s' look-and-feel in the 2025 implementations.
Actually, Smalltalk images are the original containers
I recently stumbled upon a #YouTube #Video where people are blaming/mocking themselves for not speaking perfectly #English. I don't understand that kind of #Behavior. #Why? Seriously, why? For me, it's most important that I can call an #Ambulance, report a #Fire or a #Crime in a #Foreign #Language. To be capable of socially acceptable #SmallTalk is of course also a nice #Ability to have. But dealing with an actual #Emergency is IMHO more #Important than asking a #Stranger how they feel today…
#SqueakJS—#Squeak and #Cuis full-fledged #Smalltalk can now run in any #browser.
#Kommunikation
Ich mag keinen #Smalltalk, ich finde ihn meistens zu oberflächlich und oft laufen solche Gespräche schnell ins Leere. Dieser Artikel zeigt einige Ansätze, wie man interessantere Gespräche führen kann, die Smalltalk als Ausgangsbasis haben:
Hey, it's #AmstradCPC #Smalltalk time again!
First of all, ùCPM fanzine released their 6th issue including my article introducing the project (lovely designed and printed on CPC, and great choice of illustrations, unfortunately for some of you, it's in French)
After a few days of thinking, I decided to throw away my semi-generational gc, and instead use the Baker two-space gc. It is simpler, and hopefully it's faster. The memory "waste" should be fine, I have lots of memory anyways?
> "The original versions of those classic languages cannot be used to solve modern problems"
The original versions of those classic languages are Turing complete, and consequently they can be used to solve all problems which can be solved through computation.
The original #LISP had 7 primitives: \(\texttt{cons}\), \(\texttt{car,}\) \(\texttt{cdr}\), \(\texttt{atom}\), \(\texttt{quote}\), \(\texttt{eq}\), and \(\texttt{cond}\). And the original #Smalltalk syntax could fit on a 5×7 card. That meant a novice could learn the syntax in a matter of minutes, and direct all his efforts to learning how properly to wield the power of that Turing-complete language. This was why, in the 1970s and the 1980s, many college freshmen were taught FP in Scheme (a more modern LISP) and many middle school children were taught OO in Smalltalk. These were surely the best "first" #programming languages.
#FORTRAN and #BASIC were simple, too. FORTRAN, the first high-level language, has been in continuous use since the late 1950s by engineers, who are not keyboard warriors. BASIC was invented in the early 1960s for teaching programming to non-STEM students at Dartmouth. It sired a whole generation of self-taught children in the 1980s.
Compare those to C++, Erlang, Python, Haskell, Java, JavaScript, Scala, Rust, Kotlin, and pretty much every language in popular use today. Most consider Python and JavaScript to be the simplest of modern languages. Yet, they are massive, complex languages. No 10-year-old could teach himself those, nor should he.
The original versions of those classic languages cannot be used to solve modern problems. But they should still be taught to youngsters as their first language. Throwing in the kids' faces a modern enterprise language confuses them and discourages them. Consequently, many novices never attain that state of flow, when the joy of programming gushes forth.
#Simplicity is a virtue. Self-motivated learning is virtuous.
Small talk to jedna z tych rzeczy, które dla wielu osób są zupełnie naturalne, ale dla innych stanowią istną torturę. Może i dla Ciebie? Czasem po prostu nie masz ochoty na rozmowy o pogodzie, o prawicowych trollach, czy jałowego pytania zaczynającego się od "co tam u Ciebie?" i marzysz, by w spokoju dotrzeć do celu, nie wikłając się w zbędne gadki. Jednak jak to zrobić, żeby nie być uznanym za mruka czy chama?
#poradnik #smalltalk #rozmowa #komunikacja #introwertyzm
https://marcinkaminski.pl/small-talk/
‘𝗥𝗔𝗡𝗗𝗢𝗠 𝗙𝗟𝗨𝗙𝗙 𝟴𝟱’ 
When talking about the weather isn’t your thing.
@phranck @pharoproject ist eine sehr schöne, aktiv entwickelte #Smalltalk Implementierung. Macht total gute Laune.
Willst du das Job-Angebot teilen?
️ 
= 
log
) 
<(FSM)<{ 
