6 ms·
Allow me one suggestion about Kay, it seems the man knows way too much to be understood by the average us. Not pompously, it's just that when he means A we read
by agumonkey 8y ago
Allow me one suggestion about Kay, it seems the man knows way too much to be understood by the average us. Not pompously, it's just that when he means A we read B. That led to the drift between Smalltalk OO and cpp OO. I thought it was exagerated, but smalltalk is really entirely different from cpp/java. It has the same vocabulary, but the reality is quite surprising.
Kay had education in abstract algebra, cell biology(apparently).. he was fond of old varied computing arch (burroughs). So my point is, before reading his text, do yourself a favor, dig in the litterature deeply and broadly.
- gambler 8y agoSeconded. Took me about 5 long videos and some Google searches to get into his frame of reference, but it was well worth it. The amount of useful ideas I got out of his talks is absolutely astounding. He really changed the way I think about programming, computing, user interfaces and complex system design. I am slowly watching through all of the videos from Kay I can find. A good compilation to start with: http://vpri.org/talks.htm http://vpri.org/talks.htm You can also search Vimeo for more.
- joaorico 8y agoThis is the most complete list of Alan Kay's talks I found: https://tinlizzie.org/IA/index.php/Talks_by_Alan_Kay https://tinlizzie.org/IA/index.php/Talks_by_Alan_Kay
- rgrau 8y agoYoshiki Ohshima regularly posts interesting "new" videos on his youtube channel[1]. Not only Alan Kay's talks but content produced in PARC back in the day, or relevant people around that environment. If you need a less abstract teaser before getting into the talks and "philosophy" part of the game, here's a demo of something called "Alternate Reality Kit"[2] back in 1986. Brace yourselves. 1. https://www.youtube.com/user/yoshikiohshima https://www.youtube.com/user/yoshikiohshima 2. https://www.youtube.com/watch?v=I9LZ6TnSP40 https://www.youtube.com/watch?v=I9LZ6TnSP40
- pjmlp 8y agoLearning about all the cool things that happened at Xerox, not only Smalltalk, but Lisp and Mesa/Cedar as well, completely changed my point of view on UNIX, and its shortcuts.
- espeed 8y agoThis is one of my favorite Alan Kay talks of all time (I think this is the right version, but at the time it wasn't on YouTube)... Programming and Scaling - Alan Kay https://www.youtube.com/watch?v=YyIQKBzIuBY https://www.youtube.com/watch?v=YyIQKBzIuBY There's also one where he discusses anthropology and the human universals, but the title of that talk has escaped me for years. Anyone remember what that one's called?
- adamnemecek 8y agoNo, it's due to performance. C++ oop is somewhat close to the idea (purists don't say that it's not) without sacrificing too much perf. Objective-C spends like half of CPU time in objc_msgSend. And that's ignoring the cost of "far" jumps.
- jacquesm 8y agoAnd Smalltalk - for much the same reasons - has some pretty quirky code in the VM to be able to make the concept of message passing between objects work fast enough to do real work. There is a pretty sharp dividing line in the VM between 'the elegant stuff' and 'the hack to make it all work', where the primitives are activated. Smalltalk primitives and their classes are of necessity implemented outside of the language, they 'just work' and you can not inspect their implementation within the VM because that would require you to reflect on its own implementation, which it can not do for obvious reasons. So even though Smalltalk is 'self aware' to an extreme degree that self awareness does not extend all the way to the bottom, and I don't see how that would be possible anyway. At some level you will have to make the jump between the CPU you'd like to have (the one executing Smalltalk directly) to the one that you actually have. There is this guy: http://www.merlintec.com/lsi/jecel.html http://www.merlintec.com/lsi/jecel.html who has been working on a ST hardware implementation for a long time, I am not aware of its current status. But note that even in that situation you will still be limited, but then not at the level of the VM builtins but at the level of the CPU instruction set implementing the primitives. Ideally Smalltalk would be able to transcend the boundaries of the computer it runs on sending messages to other computers with proper error handling, that would be some kind of hybrid between the BEAM and the Smalltalk VM.
- rgrau 8y agoI guess it's not the same kind of introspection because it adds a level of indirection, but I've heard stories of the VM itself being implemented in something called "slang"[1] that's a kind of lower level smalltalk that easily compiles to C, but can be interpreted in smalltalk itself (via an Interpreter class that is perfectly normal smalltalk). Information is quite sparse on that topic, and my knowledge is quite fuzzy there but I'd love to find more info on that (in case anyone can provide links.) 1. http://wiki.squeak.org/squeak/slang http://wiki.squeak.org/squeak/slang
- da02 8y agoIt might also help to know Kay has said the Internet is a good example of "Real OOP": A system made up of other systems sending messages that are "desires", not commands. (paraphrasing) (He has also been quite humble. He claims his own original ideas aren't very good and all the best stuff came from others. On Smalltalk, he also mentions Dan Ingalls did most of the work while Kay only did the mathematics.)
- agumonkey 8y agoIt's funny because he keeps ranting about how things are so subpar. It can appear un-humble at times.
- gambler 8y agoWhat if things really are subpar and you simply don't have the frame of reference to see it?
- derefr 8y ago> the Internet is a good example of "Real OOP": A system made up of other systems sending messages that are "desires", not commands. Or: OOP is what you get when you take the necessary programming model required at the software level, to get two hardware devices that don't trust each-other's engineering to successfully exchange data (like, say, a computer in a public library, and your smartphone that you've just plugged into it over USB), and then try to shrink it down as far as it'll go, while still retaining the ability to represent and handle every potential failure-mode of the original exchange.
- davidgay 8y agoThere is no silver bullet. Actors are overrated. Either you assume that any message may get lost, and you have to deal with failure, which is always painful. Or you assume the sender and receiver share a failure domain, and you're introducing asynchrony for no clear reason.
- inopinatus 8y agoErlang/OTP. Failure can be orthogonal to stability, and it doesn't have to be painful.
- walterstucco 8y agoWhat's the difference with functions that can fail or an API call that timeouts? If actors are designed to be services failure or a lost message are an implicit assumption Internally actors are fully synchronous
- espeed 8y agoThis is the draft of the original 1972 unpublished memo where Alan Kay introduces the idea of object programming: Alan Kay: A Personal Computer for Children of All Ages (1972) [pdf] http://www.vpri.org/pdf/hc_pers_comp_for_children.pdf http://www.vpri.org/pdf/hc_pers_comp_for_children.pdf NB: Double check me on that -- is this the original unpublished one, or the revised one?