[pjmlp]

Smalltalk as platform did take off, that is why the famous GoF book uses Smalltalk and C++, even though many think Java is somehow on a book that predates it for about three years.

All the IBM's Visual Age line of IDEs were written in Smalltalk, and in a way it was the ".NET" of OS/2.

SOM (OS/2 COM) supported it natively, and one biggest difference to COM is that it supports meta-classes and proper inheritance, language agnostic.

What made Smalltalk lose industry mindshare was exactly Java.

When it came out, some major vendors, like IBM, pivoted all the way into Java, leaving Smalltalk behind.

It is no accident that Eclipse was designed by some of the GoF authors, and it is initially a rewrite of Visual Age underlying platform from Smalltalk to Java.

Eclipse even to this day has a Smalltalk like code browser.

It wasn't only the IDEs, some famous Java libraries, like JUnit, started their life as Smalltalk libraries.

Now as full OS, yes that never really took off.

Note not all Smalltalk vendors switched to Java, that is why Dolphin and Cincom Smalltalk are still around.

[djmips]

And as you hint at C# later and honestly it sometimes feels like the Unity game IDE took up the throne of Smalltalk with it's Smalltalk derived language and it's interactive IDE. What do you think?

[pjmlp]

Not sure about Unity in particular, I would say that is already part of .NET given its linage, don't forget J++ was going to be the main language of what became .NET, had it not been for Sun's lawsuit.

Many of the Unity capabilities are built on top of Mono, and the reference implementation alongside Visual Studio has more capabilities still.

If you mean the game editor experience itself, yes the interactive development ideas are there, but so are they in any game engine reasonable modern worth using.

[lproven]

> the Unity game IDE took up the throne of Smalltalk

No, that would be OpenCroquet, I think.

https://www.theregister.com/2023/03/23/croquet_for_unity/

[igouy]

> not all Smalltalk vendors switched to Java

Cincom only acquired the VisualWorks Smalltalk software after ParcPlace had unsuccessfully rebranded as ObjectShare in response to the emergence of free as in beer Java.

[pjmlp]

Thanks for the overview.

Yeah, still it is quite surprising, in a positive way, that a few vendors manage to stay in business, despite all the reasons not to.

[speedbird]

Lots of things went wrong.

ParcPlace acquired competitor Digitalk and tried to create a Frankenstein hybrid - jigsaw? - that royally screwed things up.

Around the time, the industry was very exercised about a number of features that alledgedly made PP Smalltalk bad:

- non-native widgets (emulated) for windows - who cares now;

- principal deployment as a single process, not natively multi-threaded, using internal virtual threads - which actually scales better;

- must be able to run in the browser like java applets - :-)

- can't get my head round "image" model, must have individual files

This was all FUD. Developing in VisualWorks with Envy (Gemstone) centralised version control was a blissful experience I haven't seen bettered.

But yes, Smalltalk and C++ faced off in industry for a number of years for the crown and then along came Java on the OSS tidal wave that effectively destroyed the business model for VisualWorks that relied on expensive licences.

[pjmlp]

Ironically the whole way modern IDEs work with virtual filesystems, or the LSP approach, aren't much different than putting an image like layer on top of traditional filesystems.

And still don't have quite a C++ IDE experience that somehow comes close to Visual Age for C++ v4 (from Smalltalk side), or Energize C++ (from Lisp side).

[igouy]

> Lots of things went wrong.

https://wirfs-brock.com/allen/posts/914

> non-native widgets

Digitalk’s Visual Smalltalk and IBM’s VisualAge provided native widgets.