> ...There you go. Now you've seen a little bit of Smalltalk and now you hate your Ruby development environment. Have a nice day!

I switched from Ruby to Smalltalk in 2008 for this specific reason.

Do you actually work in smalltalk or is it just your hobby language of choice?

I wrote my Bachelor and Master thesis with it. I thought about working at HRWorks, but then decided to do Python and now TypeScript. I'm learning Rust now, just because how the closures look a bit similar to Smalltalk since I miss it so much.

I feel anxious looking at the multitude of windows. Do you get used to it?

it's not much more overpowering than other ides - just close anything you are not interested in.

No. This is easily the weakest part of Smalltalk IDEs. And with Morphic-based ones, you can't even fix it with a tiling window manager or something, since it's just one window for the rest of the OS. There's no way of organizing the windows in groups, no automatic placement, no virtual desktops. The best you can do is simply get into a habit of culling unnecessary windows. It's emotionally hard to close windows you spent 10 minutes searching in for the code you might (or might not) need in the future, so I made a simple sidebar[1] that I use to bookmark useful stuff. With it, I can close windows with impunity.

[1] https://klibert.pl/statics/smalltalk/sidebar.png

Yes and then you learn how use them together.

Depending on your workflow, you get used to it rather quickly imo. I recently rewrote a Python script which extracted metadata from an XML file and using that metadata to stitch together fulltext from OCR (OCR where single pages,and the metadata held references to page numbers - whoever programmed that needs to be slapped). So I worked fully in the Pharo environment, file browser to look and check, "code browser" to code and change etc. The glory really was, the extraction took quite some time (a few hours, millions of files, python wasn't really faster), but after that, I had objects in the environment and code changes reflected, I saw a wrong extraction, I could correct and run it over this single text, which with the Py script was much more inconvenient. Yes, you could code it differently to do that, but with Pharo my code didn't need to account for that. Also "oh, I need to create a new metadate like year+month", code it and its there for every text, and if I decide to have it generated on the fly, I'm done if I need it as instance variable, I run this (and only this) method for all texts, which takes a second. And then into Elasticsearch for our other pipeline afterwards ;-) Plus, close it (and save) and you when you reopen, you are exactly where you were, opened windows and all

Until I watched this I never understood class definitions in Pharo. His "we tell the TestClass to create a subclass of itself" blew my mind.

What's the usefulness of that?

The congruence with the rest of the language. It makes it so that creating a new class isn't declarative, but also just another message sent to the ecosystem of objects.

Idunno, as a Rubyist, the bit on examples was kind of cool (awful syntax though!) but my IDE already offers to create stub classes for lots of stuff.

What I don't get is why this sort of thing needs to be in its own OS. Why can't it live in my OS of choice, so I can use it to interact with things I care about?