This is a great post, thanks. I've been following prototype systems since I first logged into lambdamoo in 91, and Self is an old intellectual muse of mine but this is the first time I'd seen Korz.
You might be interested in my lang/environment "mica" which attacks this same dimension of problems from a relational/datalog angle and then makes object/prototype identity hopefully emergent out of that: https://github.com/timbran-project/mica -- relational dispatch feels like a broadening of multiple dispatch.
I feel like I may have ended up at a similar place as Korz without realizing it. I will need to dig into this paper.
Speaking also of multiple dispatch and prototypes, there's also this paper from an old acquaintance: https://www.cs.cmu.edu/~aldrich/courses/819/salzman-pmd.pdf which I used to find interesting (and built my first version of "mica" back then around the idea).
yeah, substantially agree. But I also think if only Atari and Commodore teams could have just been one company... it would have been glorious. Somehow. The market couldn't afford to be split like that, the pie wasn't big enough.
Also I was an Atari ST user back then, and loved it. But the Tramiel's didn't "get" software in the early days. They failed to make the right investments to keep TOS/GEM actively developed (e.g. as a Mac alternative) until it was too late (they hired Eric Smith to work on MiNT and then MultiTOS in the early 90s but they were already done as a company by then).
And then three fundamental hardware mistakes with the ST were:
1. not shipping it with the Blitter from the start so it couldn't compete on games, obviously with the Amiga but even with 8-bits of the time
2. forcing the ROM size down to 192kB so they had to size optimize the crap out of GEM before shipping (waste of precious development time), especially including tossing away all of GDOS (which had support for proportional fonts and printer drivers etc). A 256kB or 512kB ROM would have solved a lot of problems with what I'd think wouldn't have been an insane BOM cost bump.
3. Minor but long term annoying -- tying the cartridge port to only have 128kB of address lines. If they had given it 256kB or 512kB address ability their later expansion issues (OS upgrades etc) would have been much improved.
As for the Amiga, great machine but a) it cost too much at the start so failed to catch immediate fire (the 500 rectified this to some degree) b) interlace.
> And then three fundamental hardware mistakes with the ST were:
> 1. not shipping it with the Blitter from the start so it couldn't compete on games, obviously with the Amiga but even with 8-bits of the time
I don't think a blitter is that big of a deal, especially for games. A sprite/tile architecture would be better for games.
I wish that the ST came with the YM2203, instead of the YM2149. That would make it an even better machine for music, with the addition of 3 4-op FM voices.
Frame rates on games on the ST were terrible, which just came down to there not being enough cycles in a single frame to really move stuff around. Sprites or tiles would be great but are a bit specific. Blitter hardware subsumes all of that under a more general utility. The STe's blitter when it finally came along was great. But by then it was too late, nobody was going to make games for it because the market was too small.
Once clockspeeds got up to what the Falcon could do, it was unnecessary. But again, too late.
The Amiga also struggles with frame rates, with most games running at 30hz/25hz. There are quite a few games that have better gameplay on the Commodore 64 port than the Amiga port.
The only arcade games that use the bitmap/blitter architecture were mostly Williams games like Robotron, Joust, and so forth. Everything else was tiles/sprites, except for the Atari vector games.
Despite its obviously far lower MIPS rating the 6502 could just get more "video game" type work done in a clock cycle than a 68000. 68000 interrupt responsiveness was also pretty terrible.
Looking back 68000 had little business in video game type machines. I like the 68000 from a programming POV but it's faster for doing a pile of fast integer calculations than it is at moving memory around and responding to interrupts.
But Atari and Commodore were also imagining their machines to be targeting productivity more than games, so.
The alternative to "open weights" at this point is "American controlled."
And Dario and Sam have already made it clear that it's America First.
The rest of the world isn't going to accept a regulatory regime which imposes American hegemony. Maybe when Silicon Valley was playing all utopian like they used to. Not now.
Open weights is the most reasonable counter-power we have.
I mean, those of us with Marxian biases define it that way -- not right wingers -- and see "social democrats" in the 21st century as being the people who successively turned the term to mean instead anything-where-government-does-stuff. That's effectively what it came to mean in the US.
Notably, the definition given by Marx and other 19th century socialists (worker controlled production) is doesn't even have to involve government or the state at all. It just came to mean that once proximity to power came into play. The "soviet" word merely meant local worker councils, not a state form, for example. But once the Bolsheviks took state power, the power of the actual soviets was successively demolished in favour of a centralized one party state.
So, notably: Self-called "Marxist-Leninists" in the USSR, and Social Democrats (or "democratic socialists" in the US), and Right-wingers all far prefer the term to mean "government controls things." The latter because they can then point fingers and call things authoritarian (but somehow exempt corporate power from critique).
But it is not at all clear that 19th century socialists .. from Proudhon through Marx etc -- who coined the term -- meant this at all.
Also this hard line between "communism" and "socialism" is fictitious and very schematic. All communists call themselves socialists, and almost none of them agree on what that means.
Social democrats trying desperately to sound respectable clearly want a nice hard line there. But they also have no intention of bringing about socialism.
These are overloaded terms at this point which is part of the reason so few actually comprehend.
Even Capitalism, Communism, and Socialism can mean different things depending on the context and interpretation which is another part of the collective confusion.
If we had clear definitions, it *might* irradicate the confusion, but I don't see that happening in the forseeable future.
There's too much at stake for every involved party to clear things up.
> These are overloaded terms at this point which is part of the reason so few actually comprehend.
this is perhaps the smallest of all possible reasons that "few actually comprehend" :) yes, the left is good at eating itself, but that self-destruction is not without a lot of external assistance!
Astra 6 was a huge improvement over Sol 5.6 for UI work. I haven't tried Sol 6 yet for it (it's only been a few minutes).
The GPT / Codex models have always been "overengineer" personalities. I prefer that to "I left a pile of race conditions lying around and big gaps in testing" though, which is what I was getting from Opus at times.
But yes both Astra and Sol veer on the side of paranoid. And honestly that's better for team work. For solo work where you just want to yeet something, it can be tiring.
You learn to tame the GPT "personality" on this front by combing over once a week and asking it to find and exterminate pointless tests, clean abstractions etc.
Astra was/is superior for planning type tasks. It was capable of doing seemingly magic things with rather vague/lazy instructions ("I need to be able to test this on Windows, maybe a qemu VM or something? Shrug." ... 1 hour later "yeah i built you a whole qemu + eval windows image + harness of powershell scripts + shell scripts to retrieve & verify harness.").
And for UI work -- which is not something I do a lot of but do here and there -- it was clearly superior to 5.6 Sol.
But it also feels sloppier? Somehow. And too expensive to use.
I felt this way with Sol in the 5.6 series and was one of the seemingly few people on this earth who liked Terra for that reason. I would often have a very specific code-manipulation ask, e.g. "add a parameter to this method, ensure all callers pass it in, if there is not a logical way to derive the parameter to be passed in a particular instance, flag this in your final response", and Sol would go on some rabbit hole side quest to refactor my codebase to determine some way to derive it rather than flagging it as I had asked.
Terra had the "workhorse" quality where it could do these changes in bulk and follow directions without being too 'smart' (but sloppy) as you described. Luna was a bit too dumb and would make sloppy mistakes; I see that more as a "run these tests and format the results" sort of model. Maybe 6 Luna will be better.
I also just reread your comment and realized the naming convention is still extremely confusing with respect to ordering of [Family]x[Model]x[Number].
I also get good mileage out of Terra when I need a diligent workhorse. That's a good way to describe it. We should start using character archetypes when we describe models, it'll do more good than the dubious numbers and cherry-picked quotes. Maybe RPG character-type cliches? Myers Briggs?
Glad you pointed out the UI work. I've been doing a lot of it and it's so much better than 5.6 as UI, it's unbelievable. I give it super ambiguous instructions and it's reading my mind. I do the same thing with 5.6 and I'm correcting it for a few minutes.
Are you trying to imply that nothing OpenAI can release would justify that response and therefore the people must be bots?
Asking cuz I don't think I'm a bot [pats self], I legitimately prefer the GPT models to Anthropic's, don't like Anthropic's customer service/reliability story at all, and I welcome a massive price reduction. Seems like something I should be happy to get.
If you'd told me I'd be typing this a year ago I'd be skeptical though.
Well, they do rug pull constantly. This week and last leading up to this the cost to use Codex was overwhelmingly perceived as terrible. People running out of usage all over the place. Reddit full of people crying. I noticed it myself.
Then they do a new model launch, issue quota resets all around, and it's a party for 2-3 weeks before things return to normal.
reply