The history link gives details, but if you want a quick analogy:
Pharo & Cuis both forked from squeak at roughly the same time
Squeak = Debian
Pharo = Arch
Cuis = Alpine
Cuis has rigorously simplified, so its much easier to explore & understand the system - because there's less of it
Cuis's re-engineering of morphic is really quite brilliant. Everything is hardware accelerated vector graphics. EVEN THE FONTS are drawn that way. And they remain crisp even when zoomed (in or out) & rotated.
Pharo does have some cool stuff though. I'd love to see fuel (object serialization) & soil (a fully oo database) ported to cuis. And the big one - seaside
But its not an either-or situation. 99% 9f what you learn & do in one is applicable to the other. But if you're starting out, I would definitely recommend cuis (not implying that you wouldn't necessarily stick with it)
Is the development experience compatible with modern AI-assisted workflows? Coding agents have drastically reduced the entry barrier for playing with software projects, and I can think of some fun ideas for Smalltalk things I've been curious about.
I saw a comment saying it is, and having a coding agent able to modify a running environment is a game changer, but I haven't wrapped my head around that yet.
AI isn't my personal cup of tea, but anyway. There is a monthly "show your cool stuff" online meetup, and the most recent one was directly about one dude using AI to build his own quasi-gnome-desktop-like morphic world within cuis.
Have you considered factor? Its from the joy-inspired branch of the forth/concatenative family, but its a heavily underrated, batteries included language. Which has a bit of a smalltalk feel given its image-based deployment and the "live" nature of its tools (graphical repl, object inspectors, etc)
Factor looks like a more conventional language, with dynamic typing, automatic memory management, etc. It sounds quite far from Forth's roots as a compact assembly sequence that enables interpretation of a minimal language just barely atop the bare metal.
fallat said they were interested in teaching a 'grassroots' language. By that I think they mean something with a minimal core language and compact interpreter, so Forth seems like the better fit.
picolisp also has an interesting closing paren style by its author, with a space before closing parentheses if the open parenthesis is not on the same line:
not really. it's just pop all of the stack and return to depth 0. you can still detect imbalanced parens, but i'm not sure how it affects the provenance question of where a missing one would point out in errors.
Hmm, leaving the naked bigotry dripping from your "comment" aside (a question for mods, not me), I'll just say: preaching from a CIA-funded ISIS training manual has less in common with Islam than the Waco Branch Davidians or Moonies have with Roman Catholicism.
I thought this level of off-the-charts anti-Muslim misinformation was going out of fashion, after enough people in the West started realizing how much of a knuckle-dragging lie-strewn psyop it all was.
> the Prophet Muhammad, for example, kept a slave-concubine (Mariya the Copt) who was given to him as a gift by the Roman governor of Alexandria.
> The male owner of a female slave can either marry her off to a different man, thus renouncing his own sexual access to her, or he may take her as his own concubine, using her sexually himself.
And in practice in the modern day:
> In the Sudan, Christian captives in the ongoing civil war are often enslaved, and female prisoners are often used sexually, with their Muslim captors claiming that Islamic law grants them permission (citation) [https://books.google.com/books?id=NaVhAQAAQBAJ&pg=PT139&dq=9... ].
It may be inconvenient for those still trying to push the "religion of peace" narrative, but that doesn't mean it's not true, or that we can't talk about it.
Hey, greetings from another former nedit user. It was my refuge from emacs on my 1997 redhat setup as I was stumbling around learning the ropes (I had to keep referring To my "Linux in a nutshell" book to remind myself how to open, save & quit in emacs)
Nedit was a godsend, until I decided to look into that other weird editor (vim) that I kept hearing about (circa 1999 or so) ...
You're right that the US is not in the same universe as the Stasi was.
The US steals more data and conducts more illicit monitoring of people in a day than the Stasi ever could in a year. Its just that the Stasi lived in an analog world, so you had lots of PHYSICAL material leftover for people to point at in faux horror.
Even now, the US is busily deploying electric shock gloves whose main selling point, DIRECT FROM THE MOUTHS OF LAW ENFORCEMENT, is that they allow pain to be administered to enforce "compliance", without leaving any real evidence.
And they are being trialed in Nebraska. On ... SCHOOL CHILDREN.
(and to complete the dystopian joke, check out the name of the company selling these Dr Doom gloves)
Whats that you hear? Howls of outrage & dissaproval from the denizens of "The Land of the Free" (tm)?
Err, no. Its just the wind blowing leaves around.
You sir are the proverbial frog who has been in the pan so long, he doesn't realise he's being boiled alive
To piggyback, EVERYTHING you see in cuis is hardware accelerated vector graphics, even the fonts. You can individually zoom windows, buttons, text, anything - in or out. Rotate them. And still have crisp, elegantly rendered full-unicode (even IN code) text.
Can I suggest you take a look at Cuis Smalltalk (a simplified fork from squeak), and any of the talks given by Juan Vuletich (main author of cuis). In Cuis, Juan took morphic back to basics and updated it heavily. Now submorphs use relative geometry (not absolute), and everything is hardware accelerated vector graphics - EVEN THE FONTS.
Seriously, reading Unicode enhanced code in a 45 degree tilted editor window, while zooming in and out just for kicks (all of this can be done by manipulating the morph with its halo's menu) just to see how crisp everything is - thats FUN!
Also, try taking apart the standard system browser (4 panes + editor), rearrange everything as per your tastes (by drag & drop), and ... everything still works
Let's see. They were part of the US military, right? In just this war alone, they started by triple tapping an ELEMENTARY SCHOOL, murdering nearly 200 little children.
And on the same day, they attacked a SPORTS STADIUM, completely vapourising a women's volleyball team who were in the midst of a game.
And that was just ... DAY ONE.
By now, we should be asking - if you're a member of the US military on active duty in an active war - prove that YOU DIDN'T kill a child, mother, handicapped person in a wheelchair, or a grandpa.
- Built as part of an IRGCN base (that base was closed in 2013)
- Within 100 yards of the perimeter of an active IRGCN base at the time of the strike
- Targeted as a result of extensive use of Palantir's Maven Smart System and Claude by the US military to pre-identify targets
Given all of that, I think the most accurate takeaway would be that the US military is deficient in their target approval process. (Arguably grossly so, though that's an international law legal question)
There's been less investigation into the background behind the Lamerd sports hall attack, but it's fairly certainly an intended US strike, likely for the same reason that the Azadi stadium was hit: assumption that it would be used as a muster point for an Iranian military response.
My takeaway from the atrocities is that there need to be substantial updates to international laws of war around (a) automated target approval (even worse excesses by the Israelis in the initial Gaza strikes) and ultimate human responsibility and (b) more strongly defining what constitutes due diligence in intelligence and classification of military targets.
Currently, both are far too nebulous and will likely lead to both incidents being classified as war as usual. Whereas there was a plausible route to both being removed as targets with even non-manual open source intelligence scraping (substantial patterns of school activity over years and the volleyball game schedule, respectively).
Pharo & Cuis both forked from squeak at roughly the same time
Squeak = Debian
Pharo = Arch
Cuis = Alpine
Cuis has rigorously simplified, so its much easier to explore & understand the system - because there's less of it
Cuis's re-engineering of morphic is really quite brilliant. Everything is hardware accelerated vector graphics. EVEN THE FONTS are drawn that way. And they remain crisp even when zoomed (in or out) & rotated.
Pharo does have some cool stuff though. I'd love to see fuel (object serialization) & soil (a fully oo database) ported to cuis. And the big one - seaside
But its not an either-or situation. 99% 9f what you learn & do in one is applicable to the other. But if you're starting out, I would definitely recommend cuis (not implying that you wouldn't necessarily stick with it)
reply