4 ms·
This is awesome! I had the honor of first learning Smalltalk (and C++ and a bit of object databases) in a class taught by Bob Beck from Sequent. We actually h
by neilv 6y ago
This is awesome!
I had the honor of first learning Smalltalk (and C++ and a bit of object databases) in a class taught by Bob Beck from Sequent. We actually had many students running Smalltalk on X terminals hanging off a Sequent server. https://en.wikipedia.org/wiki/Sequent_Computer_Systems https://en.wikipedia.org/wiki/Sequent_Computer_Systems
Smalltalk was a crazy-productive programming environment in the '90s, and easy to love. (A bit like Lisp, in that regard, but also very different.)
What's even more amazing than that PARC was doing this in the 1970s, was that what we know as Smalltalk was only one part or step towards grand goals they were heading towards, not the end product. http://worrydream.com/EarlyHistoryOfSmalltalk/ http://worrydream.com/EarlyHistoryOfSmalltalk/
When we find ourselves strutting around about how smart we are, how we'll change the world, as we move fast and break things (with what power we can seize and exercise over our users, with our app)... a needed dose of humility comes from seeing that the Smalltalk (and other) people, of decades earlier, seem a thousand years ahead of where we are now, in thinking.
- phtrivier 6y agoAccording to "What the Dormouse said" [1], there were a couple main differences between them and us: 1. They grew up in a world without personnal computers, and had the time to _read_ _books_ ; 2. They had the pressure of either coming up with very bright ideas to impress their Pentagon-related funders, or get send to play real-life Call of Duty in Vietnam ; 3. They were almost free to invent whatever they had in mind since the class of "managers / deciders which no technical roots" had not really emerged yet ; 4. They were periodically high on LSD. Whereas we're mostly now working in a billion dollars industry with strong incentive for conservativeness of products, with a pop-culture discipline rather than engineering culture, where it's pretty easy to get "something" on the screen, lots of high paying but menial jobs available - and we have to do it only on coffee ! [1] https://en.wikipedia.org/wiki/What_the_Dormouse_Said https://en.wikipedia.org/wiki/What_the_Dormouse_Said
- pjmlp 6y agoWhich is why I was only impressed by UNIX until I started digging into Xerox PARC work, and its influences on Apple Lisa/Mac and ETHZ Oberon derived OSes. The few UNIX variants that I actually still find interesting was the NeWS approach, NeXTSTEP and its descendants.
- Rochus 6y agoETH Oberon was not derived from Smalltalk. I implemented both systems, see https://github.com/rochus-keller/Smalltalk https://github.com/rochus-keller/Smalltalk and https://github.com/rochus-keller/Oberon https://github.com/rochus-keller/Oberon and can say for sure they have very little in common. Wirth was inspired by the Alto, Dorado and the Mesa and Cedar programming systems. The Alto OS (the first GUI desktop and WYSIWYG word processor and DTP applications Bravo and Gypsy) was implemented in BCPL (precursor of C), not in Smalltalk. Many people seem not to know, but you can look at all the source code at the Computer History Museum.
- pjmlp 6y agoI have explicitly not stated anything about Oberon being derived from Smalltalk, rather from Xerox PARC "w̲o̲r̲k̲".
- Rochus 6y agoThis is a thread about a Smalltalk-80 VM.
- rjsw 6y agoThere were common style elements across all the Xerox PARC software systems, the one not mentioned so far is Interlisp-D. I don't think you can claim that Wirth was only influenced by the BCPL and Mesa group.
- pjmlp 6y agoIn fact, Mesa and Mesa/Cedar developers explicitly refer to their goal to replicate Smalltalk and Interlisp-D developer experiences on XDE and Cedar, across their papers.
- Rochus 6y agoThat only applies to the Cedar programming environment. Show me the references otherwise pls. And it was even more remarkable that Xerox did not use Smalltalk for its GUI applications and the systems after Alto.
- poulsbohemian 6y ago>Smalltalk was a crazy-productive programming environment in the '90s, I did some in college and then professionally in the early 2000s. Easily the most enjoyable and productive tool I used in my software development career. While I understand HNs fascination with functional languages and programming, I can't help but think it is very unfortunate that Smalltalk and it's OOP has been left as a kind of evolutionary dead end.
- int_19h 6y agoThe modern fascination with "functional" is, in part, because we have redefined "functional" to apply to basically any language with first-class anonymous functions that are closures - witness all the talk about "functional JS" and how it's "almost like Lisp". By that criteria, Smalltalk was one of the first industrial-strength functional languages. In fact, it's better than most, because its closures close over not just the variables, but also over the execution context (i.e. a closure can execute a non-local return from the function in which it was created).
- lispm 6y agoThough, early Smalltalk did not support lexical closures.