Reminds me of the "Liberating the Smalltalk lurking in C and Unix" talk by Stephen Kell: https://www.youtube.com/watch?v=LwicN2u6Dro
The Unix Executable as a Smalltalk Method [pdf]
11–20 of 24 posts
Re: The Unix Executable as a Smalltalk Method [pdf]
#12Funny, and the persistent memory-image everyone outside the Smalltalk/Lisp community seems to hate, it's your normal filesystem now.
The irony is that anyone using IDEs is using the same idea, as all of them use a virtual filesystem layer to simulate the same capabilities as the image approach.
Re: The Unix Executable as a Smalltalk Method [pdf]
#13[deleted]
Re: The Unix Executable as a Smalltalk Method [pdf]
#14Reminds me of the "Liberating the Smalltalk lurking in C and Unix" talk by Stephen Kell: https://www.youtube.com/watch?v=LwicN2u6Dro
Thanks I was looking for that. I've seen a video about that some time ago and couldn't remember the name or the anything.
For those interested here's a link to the actual project:
Re: The Unix Executable as a Smalltalk Method [pdf]
#15I recall someone, maybe Alan Kay, saying that object oriented programming was a bit of a misnomer. A better description of what they were getting at was message oriented programming, replacing the notion of blocking function calls with message passing. Objects were just a way of grouping state with functions and were less significant.
Re: The Unix Executable as a Smalltalk Method [pdf]
#16Funny, and the persistent memory-image everyone outside the Smalltalk/Lisp community seems to hate, it's your normal filesystem now.
The irony is that anyone using IDEs is using the same idea, as all of them use a virtual filesystem layer to simulate the same capabilities as the image approach.
Not really, because you still recompile and start the program from scratch, rather than modifying the code that executes on the still-existing data structures.
Edit: rather than just naysaying, it occurred to me to reference the notion of Orthogonal Persistence, which the image-based approach provides (not without drawbacks) but IDEs typically don’t. Previous HN discussion: https://news.ycombinator.com/item?id=39615228
Re: The Unix Executable as a Smalltalk Method [pdf]
#17I recall someone, maybe Alan Kay, saying that object oriented programming was a bit of a misnomer. A better description of what they were getting at was message oriented programming, replacing the notion of blocking function calls with message passing. Objects were just a way of grouping state with functions and were less significant.
Yes it was Alan Kay.
https://wiki.c2.com/?AlanKayOnMessaging
Another relevant page on the same site is: https://wiki.c2.com/?AlanKaysDefinitionOfObjectOriented
Re: The Unix Executable as a Smalltalk Method [pdf]
#18Earlier quoted context omitted.
The irony is that anyone using IDEs is using the same idea, as all of them use a virtual filesystem layer to simulate the same capabilities as the image approach.
Not really, because you still recompile and start the program from scratch, rather than modifying the code that executes on the still-existing data structures. Edit: rather than just naysaying, it occurred to me to reference the notion of Orthogonal Persistence, which the image-based approach provides (not without drawbacks) but IDEs typically don’t. Previous HN discussion: https://news.ycombinator.com/item?id=396152…
Kind of, see Cadilac model for Energize C++, born out of Lucid Lisp.
Re: The Unix Executable as a Smalltalk Method [pdf]
#19As a Smalltalk dork (Jaya Dan Ingalls!) and a former UNIXtard this really gets me moist as hell.
Semi-related; anybody have an old NeXTcube they'd be willing to part with? I'm a student and I need it for school and things.
Re: The Unix Executable as a Smalltalk Method [pdf]
#20Reminds me of the "Liberating the Smalltalk lurking in C and Unix" talk by Stephen Kell: https://www.youtube.com/watch?v=LwicN2u6Dro
Thanks I was looking for that. I've seen a video about that some time ago and couldn't remember the name or the anything. For those interested here's a link to the actual project: * https://github.com/stephenrkell/liballocs
Probably a lot of overlap with the links upthread, but [0] also goes over Unix and Smalltalk (and I only just realized is also by Stephen Kell).