111–114 of 114 posts
Earlier quoted context omitted.
unfortunately, it's not really the same as with proper message passing/late binding like in smalltalk.
You could use C# dynamic objects to achieve late binding.
I've used Pharo, and, way back, programmed professionally in Cincom (then ParkPlace), IBM VisualAge, and whatever the Windows version of Smalltalk was called was called (Visual Smalltalk?). Also tooled-around a bit in Squeak. All three of the professional environments were very good. When Pharo kicked off, it was supposed to have been people building a free Smalltalk you could use to build real world software, as opp…
It is like fitness. One just hates it when it aches all over the place and then quits. Or keeps on moving through the pain/grind and grow a lot in all kinds of ways. And saying that VA or VW give a better user experience when coding vs Pharo, I beg to differ.
Earlier quoted context omitted.
The reason is Stéphane Ducasse is using his students as unpaid testers[0]. I can't see any other reason he'd make us use the latest technologies as you mentioned. I also don't like the approach "let's write some code that passes tests and maybe works 80% of the time, and then release a few fixes every week for the next few months". Some of my classmates had to wait for 2 weeks just to get a working version of iceberg…
Martin, IIUC you are a student that suffered a class using bleeding edge features. I can understand why you are bitter, but you should not be so quick to disparage Mr Ducasse. Your faculty was his client, and it seems that circumstance was outside his control. From our mail list... Stephane Ducasse wrote: > I told them NOT to use github. > I told them that Bloc was alpha. They got a large list of topics and could hav…
OTOH, please note that iceberg was only the tip of the iceberg (i am a huge fan of the name), the IDE itself did crash many times and corrupted my image once. The formatter moved comments into other blocks which changed their meaning and combined with CTRL+Z it deleted code after cursor in some cases reproducibly.
One extra funny though harmless bug was that shift+click didn't select a range of items items in some listboxes. It selected just the new one but left the old one highlighted. I clicked a few items and sometimes it selected the whole range. When I released shift and clicked more items, it played back the clicks i made earlier and selected those items instead. We joked that smalltalk did not only invent OOP but also command queuing in strategy games. Yeah, it was mean but we couldn't imagine what code had to be behind the listboxes to cause this behavior.
So yeah, maybe someone else thought OOP students would make a good typechecker for iceberg and designed the class accordingly but what i think and say about pharo still stands.
I see many comments talking about teaching objects with Pharo, we used to use it in the UNQ (a university in Argentina), now we use another Smalltalk flavour, because of the complexity of it. It's called CUIS, developed in Argentina too, the first days we use a framework that uses some similar to prototypes, so the students can start learning objects without the overhead of classes and inheritance. And then we switch…
Yes, Juan and community have done a good job with Cuis. Cuis is a fork of Squeak same as Pharo, and all three use the same OpenSmalltalk-VM. Both forks arose to deal with a large technical debt in different ways. Cuis has been paring back class sizes while Pharo has been focused on a full source-code only bootstrap from a null-Image (i.e. no carried over state in an Image, that is one of Smalltalk's typical criticism…
https://github.com/hernanwilkinson/Cuis-Smalltalk-Denotative...