6 ms·
The Early History of Smalltalk (1993)
- deleted 5y ago[deleted]
- rwmj 5y agoThis video of Dan Ingalls demonstrating SmallTalk on an Alto didn't get any traction when I posted it, but it's really quite interesting: https://news.ycombinator.com/item?id=30882555 https://news.ycombinator.com/item?id=30882555
- macintux 5y agoI’m not very far in yet, but three thoughts: * thank you, thank you, thank you (that’s only one thought) * the fact that Smalltalk is objects all the way down (methods, stack frames) is impressive * his camo shirt (look at the chair) is quite distracting
- ModernMech 5y agoOne thing I'm wondering about is, what's with the cursive-ish font? It seems like a very bad time for coding. Doing some searching now I can't seem to find a reference (hard to know what to search for, Google thinks I might mean recursive). Does anyone have an idea?
- spindle 5y agoCould it be Cream? https://lists.cuis.st/mailman/archives/cuis-dev/2022-April/005370.html https://lists.cuis.st/mailman/archives/cuis-dev/2022-April/0...
- ModernMech 5y agoThat must be it! Thanks!
- Jtsummers 5y agoI've been on a Smalltalk kick the last couple of weeks (studied/used it in college, remembered many of the ideas but had never done a proper deep dive before). This was one of the papers I read and found particularly interesting, not just for its talk about Smalltalk itself but also about teaching programming (both to kids and adults). There have been several past discussions. Ones with more than 1 comment: https://news.ycombinator.com/item?id=25012425 https://news.ycombinator.com/item?id=25012425 - Nov 7, 2020 (28 comments) https://news.ycombinator.com/item?id=17913668 https://news.ycombinator.com/item?id=17913668 - Sept 4, 2018 (69 comments) https://news.ycombinator.com/item?id=9907556 https://news.ycombinator.com/item?id=9907556 - July 18, 2015 (5 comments) https://news.ycombinator.com/item?id=9588316 https://news.ycombinator.com/item?id=9588316 - May 22, 2015 (5 comments) https://news.ycombinator.com/item?id=7926141 https://news.ycombinator.com/item?id=7926141 - June 21, 2014 (10 comments) https://news.ycombinator.com/item?id=1311282 https://news.ycombinator.com/item?id=1311282 - May 1, 2010 (17 comments)
- igouy 5y agoYou may find this interesting: "Smalltalk at Tektronix" STIC13 2013 https://www.wirfs-brock.com/allen/files/tek/Tek-Smalltalk-history-slides.pdf https://www.wirfs-brock.com/allen/files/tek/Tek-Smalltalk-hi...
- no_wizard 5y agoHere's an archive.org link to the site, since HTTPS doesn't appear to be valid https://web.archive.org/web/20220420150543/http://worrydream.com/EarlyHistoryOfSmalltalk/ https://web.archive.org/web/20220420150543/http://worrydream...
- Jtsummers 5y agoNow that this is back here and I've realized it (thanks second chance pool!) some other content you may find interesting if you liked this one: Dan Ingalls' Evolution of Smalltalk: http://worrydream.com/refs/Ingalls%20-%20The%20Evolution%20of%20Smalltalk.pdf http://worrydream.com/refs/Ingalls%20-%20The%20Evolution%20o.... This covers some of the same time period as Kay's article but goes on through the early commercial history of Smalltalk and the development of Squeak. Lots of free books courtesy of Stéphane Ducasse and the people who released them for free and OCR'd them: http://stephane.ducasse.free.fr/FreeBooks/ http://stephane.ducasse.free.fr/FreeBooks/. I'm reading The Bluebook, Smalltalk-80: The Language and its Implementation by Goldberg and Robson, presently. And if you either don't want to install Smalltalk on your system or want to use an older version: https://smalltalkzoo.thechm.org/ https://smalltalkzoo.thechm.org/. With a writeup about it here: https://computerhistory.org/blog/introducing-the-smalltalk-zoo-48-years-of-smalltalk-history-at-chm/ https://computerhistory.org/blog/introducing-the-smalltalk-z...
- galaxyLogic 5y agoI can recommend the book "Smalltalk Design Patterns Companion" for the purpose of - learning Design Patterns. Because of Smalltalk's simplicity the design patterns' "essence" comes through more easily than in a clunky low-level language like C++. This book also provides good examples of what good Smalltalk code looks like.
- sebastianconcpt 5y agoI endorse this one strongly!
- cubano 5y agoFucking Smalltalk... This...what do you call it? A mindset? A way of life? The answer to all questions? Because you cannot simply call it a programming language that's for sure. I started programming in 1979 and throughout my long career I have constantly been exposed to various Smalltalk articles and genuflections. Wow! Just look! Fucking EVERYTHING is an object! Holy shit can you believe the audacity of the developers? Along with LISP, Smalltalk is just one of Holy Shrines That One Must Visit In Order To Complete One's Path As A Real Programmer. I almost think "Ancient Religion" should be the right moniker...
- gjvc 5y ago>I started programming in 1979 and throughout my long career I have constantly been exposed to various Smalltalk articles and genuflections. With that experience, what do you think of the state and directions of the computer industry today?
- a4isms 5y agoI started programming around 1972 or so, so we are likely of similar vintage. I think we tend to find what we seek. I have found much to learn from Smalltalk and Lisp in the fifty years since I first wrote FORTRAN programs on punch cards at UofT's High-Speed Job Stream, and while yes, there are various people whose enthusiasm and narrow focus rivals any religious cult... Here's the thing. Some people will hate a thing so much they'll accuse you of professional misconduct for using it. Seriously, you can find people who say, in writing, that programming without static type-checking is professional misconduct. Should that stop us from using JavaScript, Clojure, Ruby, Python, &c.? No. Although hey, at least read their arguments with an open mind and decide for yourself. On the other side, there will be people who love a thing so much that they can't imagine using anything else. We may not love it as much as they do, but should that stop us from using that thing if we like? Also no. Bottom line: Why judge a thing by what the most extreme opinions about the thing are, or how extreme those opinions are? Judge by its utility for you.
- igouy 5y ago> Because you cannot simply call it a programming language that's for sure. Programming language + windows, icons, menus, pointer + editor + source debugger + source libraries (including compiler, wimp, editor, debugger) + graphics libraries Back when each of those cost extra, Smalltalk/V 286 was an affordable development tool ;-) March 7, 1988 — "Smalltalk/V 286 is available now and costs $199.95, the company said. Registered users of Digitalk's Smalltalk/V can upgrade for $75 until June 1." https://books.google.com/books?id=CD8EAAAAMBAJ&lpg=PA25&ots=jiXJNN0ii3&dq=digitalk%20v%2F286&pg=PA25#v=onepage&q=digitalk%20v/286&f=false https://books.google.com/books?id=CD8EAAAAMBAJ&lpg=PA25&ots=...
- Mikeb85 5y ago> Philosophically, Smalltalk's objects have much in common with the monads of Leibniz and the notions of 20th century physics and biology Love this line as this was definitely my impression of monads when venturing into Haskell-land... The whole history of Smalltalk is interesting and it's an interesting way to reason about data and behaviour. And even if Smalltalk is obscure, C++, Java, Ruby, Python and others aren't, and OOP remains a great way to model many domains.
- chillpenguin 5y agoI could be wrong because I don't know much about Leibniz's monads, but aren't those a completely different thing from Haskell monads? I don't just mean "slightly different" like how arrays in javascript are slightly different than arrays in C. I mean like they are completely different ideas/concepts that happen to share the same word. I think "Homonym" is the right word for this situation?
- deleted 5y ago[deleted]
- coldtea 5y ago>Love this line as this was definitely my impression of monads when venturing into Haskell-land Despite the name though, Leibniz monad's don't have anything to do with monads in category theory/math and Haskell. In Leibniz the name monads is used for a philosophical concept, kinda like a blend of "atoms" in Democritus and platonic "ideas" ("https://en.wikipedia.org/wiki/Monadology https://en.wikipedia.org/wiki/Monadology")
- spindle 5y agoSpecifically, Leibniz's monads couldn't have any communication of any kind with anything (including each other or themselves), so they are not really a great model of anything in computer science!
- eric4smith 5y agoSmalltalk is cool. But… For what? Practically speaking in 2022 it has no benefit over any other system or language or libraries. It seems to be a cool thing that we can talk about as we look at our college days with nostalgia. A few people will even vehemently insist that they use it just as well today and it’s the “best thing ever” and you ingrates and peons belonging to the uneducated and unsophisticated masses should use it. So we guiltily head over to the smalltalk language site and maybe even do a brew install. And yes it looks neat! Damn, if we were in a different world then everyone should be using it! But what’s that? I see the weekly e-mail report on traffic and revenue from my ruby app. As I head off to my home and family to plan our monthly weekend vacation at the lake cottage paid for by my 9-5, I’ve forgotten about smalltalk until the next HN article…
- JKCalhoun 5y agoMan, you're harshing my buzz.
- eric4smith 5y agoHahaha
- smackeyacky 5y agoI'm of a similar opinion (having been a Smalltalk developer in the 1990s boom) but I think it's worth looking at for modern programmers. I wouldn't use it for anything myself any more, but for me it's a nice way to get the flavour of the work being done in the AI community and at Xerox Parc in those days. Like a history book you can crawl into rather than just experience vicariously. One thing I do find interesting is that the programmers who usually come up as "legendary" in this context were usually just better than average guys who ended up in the right place at the right time. A lot of their code is still running in the Cincom VisualWorks product and not all of it is gold.
- galaxyLogic 5y agoIs VisualWorks still a product?
- galaxyLogic 5y agoHaving worked with Smalltalk a lot I think I know what its main flaw for industrial software development is. It is the image, and your ability to change anything in it (easily), like the Compiler for instance. Then you save your image. Your image is no longer compliant with anybody else's image and the programs you develop "on it" will not run on anybody else's image. Compare this to a language like JavaScript. There too you can modify the base-objects like Object and Function and Array. But the changes you make to them will be part of your program which is not saved as part of an "image" (only as source-code). Your JavaScript program does not assume anything more about its environment than anybody else's JavaScript program, because you can not develop against a modified "base-image" (since there is no such thin in JavaScript, is there?). Smalltalk would be great for things like programming all the smart devices in your house. I think that was part of its original goals, provide an environment where everybody can create their own programs, without worrying much about how your program might later integrate with programs of others.
- xkriva11 5y agoI must disagree. Image concept is just a tool, and it only depends on how you use it. In Smalltalk, you can modify the "base-objects" and assign these changes to your package and export them with the other sources (managed by Git, for example), so there is no difference to JavaScript here. But unlike JavaScript and others, you can use the image for things like saving the system state with a debugger open on a bug that is very rare and hard to reproduce.
- galaxyLogic 5y ago> it only depends on how you use it. It is a tool which is very easy to misuse, by forgetting to file out all the changes you make to it. That is not uncommon in practice. Most (or all?) Smalltalk's come with an image, but there is no source-file telling you how that image was derived, or how you can derive it from some more basic "standard" vanilla image. That is the reason why it is so difficult to get code developed on one Smalltalk -platform to work on images provided by other vendors. You could say that is caused by "misuse" of the image-tool, but seems like all Smalltalk vendors are doing it.