Anyone seen an #ActivityPub library written in #Scheme (any flavor) or #Smalltalk ?

I'm not finding any sign of either.

[edit: thanks folks. Turns out @cwebber wrote one in Guile. https://gitlab.com/dustyweb/pubstrate ]

Perhaps I should take some bigger examples of my private programming history. Those are often similar or better than my professional projects using these languages. And then AI should rate #style, #readability and #maintainability, perhaps room for optimization without loosing these criteria. The languages here would be #pascal, #perl, #python, #java, #smalltalk, #erlang and #golang. Should be interesting. And beside the different languages I would expect a reflection of my personal experience.

Maybe my website will be a self-hosted web based Smalltalk image that you simply run and explore in your own browser:

https://squeak.js.org/

I _completely_ love that this exists.

#smalltalk #fediverse is there a way to bootstrap a Pharo environment without Pharo?

#Smalltalk -80 on #PERQ --- Mario Wolczko's implementation running with maybe some gremlins still to sort out. attn @skeezicsb as usual

Dan Banay's #Smalltalk-80 "By the #Bluebook" implementation—tis a product of love!

https://github.com/dbanay/Smalltalk?tab=readme-ov-file

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/

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 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.

#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:

https://utopia.de/ratgeber/unangenehmen-small-talk-vermeiden-einfacher-trick-macht-gespraeche-viel-interessanter_797050/

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 #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.

Lesson 4: Programming the Shooter Game in Squeak/Smalltalk https://news.squeak.org/2025/03/14/lesson-4-programming-the-shooter-game-in-squeak-smalltalk/

Wanting to go outside to start my biochar vs. Being perceived by the neighbour who is cleaning his mowers and would enthusiastically like to mow my lawn to an inch of it's life for free.

#dilemma #notQuiteAnHOABut #auDHD #hiding #smallTalk #actuallyAutistic #theDread

@actuallyautistic