Live data from Hacker News

Today’s Smalltalk: A Second Look At The First OO Language

blog.smartbear.com

51–52 of 52 posts

Re: Today’s Smalltalk: A Second Look At The First OO Language

#51
post #48

Earlier quoted context omitted.

Closures as a form of encapsulation is actually very lispy. Simula introduced classes while Sketchpad introduced prototypes (predates Simula by 5 years), so both were very much proto OO in that sense. But if it makes you feel any better, we could define proto OO just to mean OO before that was a term anyone invented.

It's not closures I described. I don't remember if Simula even have closures or not - it's possible it does. The mechanism I described involves message passing between co-routines. In any case, I detest Simula with the kind of burning hate you can only experience after having been forced to use it (it was the language used in a compulsory CS course; though admittedly most of my hate stems from the horrible standard l…

Co-routines are based on what I would call closures (they just continue running rather than returning a value to be called!).

Surely you weren't using Simula 1 or Simula 67 in your courses?

Re: Today’s Smalltalk: A Second Look At The First OO Language

#52
post #7

Earlier quoted context omitted.

And yet people are talking about using VM images and the likes of Docker for deployment nowadays.

There is definitely a level where the concept makes a lot of sense, but even with things like docker or vagrant or ec2 images there is still an expectation that you keep around enough information to replicate the image from scratch, be it a shell script or chef or puppet or a dockerfile. Smalltalk's images didn't really have this feature.

We are working on bootstrapping Pharo from source. Have a look here: https://github.com/guillep/PharoKernel But it's tricky and I guess it will take until Pharo4 or Pharo5 until this is in the main release
Post reply on HN