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

I'm not finding any sign of either.

Wenn sich Menschen zu (fortlaufenden) Kursen oder Festivals beim Improtheater treffen, ist selten (oder erst sehr spät) die Rede vom beruflichen Hintergrund der Einzelnen.

Generell bewege ich mich in vielen Kontexten, in denen das Berufliche keine Rolle spielt.

Deswegen bin ich negativ überrascht, wenn ich auf „ganz normalem Wege“ eine neue Person kennenlerne und die gleich nach meinem Beruf fragt (und sortiere sie meinerseits in die Schublade „einfach gestrickt“ ein).

Maybe this is what @loke tried to tell me another day.

Pharo class variables can be defined as 'slots:' too, but I had to choose 'Class side' (radio button) first.

https://functional.cafe/@loke/114789870637046992

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.

Heute gelernt: Obwohl beispielsweise im Smalltalk Buch von Strahringer und Kaufmann behauptet wird nil stünde „Not In List“, gilt als gesichert, dass die Angabe im bekannten Buch von Abelson und Sussman, es handele sich um eine Kontraktion von „nihil“ (lat. nichts), die korrekte Herleitung ist. #TIL #Scheme #Smalltalk #Oberon #Pascal

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

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.

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.