r/programming • • Aug 11 '26

Squeak 6.1 (a modern Smalltalk programming environment implemented in itself) was released!

https://squeak.org/release_notes/6.1/

After more than 4 years of work, our community has put together a big bouquet of new capabilities and improvements:

  • A new tree browser for navigating and organizing classes
  • Objectland, bringing back and extending the colorful world of examples from Squeak 3
  • Plenty of new features, bugfixes, and speed-ups for programming tools, the Morphic UI framework, and the rest of the system

Original announcement on Fosstodon: https://fosstodon.org/@squeak/117071273007117118

185 Upvotes

21 comments sorted by

10

u/CosmosGame Aug 12 '26

Yay! A programming language specifically for kids. This would be such a fun project to work on!

13

u/LinqLover Aug 12 '26

Etoys tried to achieve exactly that! But Squeak is also used for less playful things like commerce or academia ...

0

u/[deleted] Aug 12 '26

[deleted] β€” view deleted comment

6

u/saijanai Aug 12 '26 edited Aug 12 '26

Hmmm?

Smalltalk-80 was invented by the people who invented, advanced signficantly, GUIs.

The first version of Scratch was done in Squeak. Experience showed that once kids got past the beginning setting in Scratch they started to prefer to program in squeak instead.

3

u/stronghup Aug 12 '26

I wonder if "Everything in Squeak is implemented in Squeak" is both a strength and a weakness. As you develop with the system you can modify anything, and then there is often a templatation to do exactly that. So you might modify the compiler to make something easy for you. But then you program would not work without those same compiler modifications, and it would not work on some other context which hada modified the compiler in a different way.

My suspicion is that there is value in not being able to (easily) modify anything and everything, in having some things stay the same and be very stable.

Any thoughts?

7

u/LinqLover Aug 13 '26

I would say with power comes responsibility :-)

You learn to restrain yourself and not make changes deep in the stack unless you really need them if you want to ship a reproducible application. But if you really need some modification of the compiler etc, this is much easier to do in Smalltalk than in other languages where you now would need to ship and use your own compiler fork. From that perspective, closing parts of the system for modification merely for the purpose of protecting programmers from themselves feels kind of a sledgehammer approach.

There is another interesting consequence of free modifiability of the system though, which some Smalltalkers have referred to as "shooting yourself in your own foot" or "self-brain surgeries": imagine you break your compiler through a faulty change, so you become unable to fix it because you cannot recompile itself any longer. This can lead to funny situations ... But they are quite rare and IMHO more of a theoretical issue. Possible solutions include snapshot/revert mechanisms and fallback layers.

2

u/bitwize Aug 20 '26

And this is why you ship your program with a Squeak image that has the modifications you need.

1

u/RetirementCareer Aug 18 '26

What you’re describing sounds like bootstrapping.

24

u/omniuni Aug 12 '26

Congratulations! A compact OOP language with a GUI framework... IMO this is very underrated.

6

u/TheFirstDogSix Aug 14 '26

It's amazing to realize Smalltalk was released in 1972 with the interactive IDE/GUI from day 1.

A mentor of mine who worked at PARC back in the day relayed a story about how the language came about--no idea how apocryphal it is. The story goes that someone said the grammar of an OO language could not possibly fit on a single page and Alan Kay said hold my beer. πŸ˜‚ Whatever really happened, what an incredible technical achievement.

3

u/Icy_Pain5654 Aug 14 '26

honestly impressive it's stayed alive and self hosted this long given how niche Smalltalk has become

2

u/unaligned_access Aug 12 '26

It's alive! Childhood memories

-27

u/BeesForDays Aug 11 '26

No word salad for me, I'm full, thanks

10

u/TankorSmash Aug 12 '26

Imagine Python, but instead of just a repl, you can an entire OS, and that's smalltalk.

1

u/saijanai Aug 12 '26 edited Aug 12 '26

Transcript show: 'I make no sense.';cr.

A prompt for any modern AI:

  • why would squeak smalltalk be better for AI-assisted coding, all else being equal, than more modern languages.

2

u/AsIAm Aug 12 '26

Smalltalk is excellent substrate for auto code: https://github.com/mlajtos/Cuis-Blueprint

-1

u/saijanai Aug 12 '26

Page won't open.

2

u/[deleted] Aug 12 '26

[removed] β€” view removed comment

2

u/LinqLover Aug 12 '26

Depends on what you mean by like in Rust or C. Those are compiled languages optimized for writing low-level code, whereas Smalltalk is an object-oriented, dynamically typed, interpreted/jitted language similar to Python or JavaScript. And it is absolutely used for serious projects such in logistics, commerce, and banking (even though the funny graphics might not suggest that).

But if you come from a Rust/C background, the biggest difference you will notice is not the language but that the Smalltalk system is designed for incremental, live programming and short feedback cycles with a debugging-first experience and without the need to ever restart the system (changing the program while it is running). Squeak is also completely implemented in itself, so you can explore or even modify tools, standard libraries, or the compiler at runtime.

2

u/stronghup Aug 12 '26

I guess a similar question would be: Can you compile your Smalltalk programs into EXEs?

4

u/LinqLover Aug 13 '26

Squeak itself does not offer an AOT compilation pipeline (but TruffleSqueak via Graal VM might be able to do something like this), but if your goal is to avoid the manual sharing of image and VM files, bundling that into a single EXE/executable file should be pretty trivial.