4 ms·
Smalltalk brought both fascinating and terrible aspects. Everything is inspectable, discoverable, interactive. Reactive programming, live objects, build stuff
by nine_k 5y ago
Smalltalk brought both fascinating and terrible aspects.
Everything is inspectable, discoverable, interactive. Reactive programming, live objects, build stuff and see it come alive at every step. JIT makes everything fast, eventually.
But also the whole thing is one huge global mutable state. You used to be able to redefine "constants" like true by mistake. You want to save the entire system image, because now everything works, but you're not sure how exactly did you end up with it during the interactive session. Static checks and guarantees are hard to have at best.
AFAICT, initially Alan Kay tried to build something like Erlang: hence messages and protocols, objects keep their state as if they were nodes of a network. But hardware limitations did not allow yet back then, so the design changed, and was still hugely influential.
I think certain languages end up being bellwethers and test beds, without becoming industry mainstays. Haskell and OCaml don't have much industry adoption, but Rust does. APL (and even k) don't have much industry adoption but numpy and spark (admittedly both libraries) do. Smalltalk and Self don't have much industry adoption but Ruby and Python do.
- pavlov 5y agoI've never understood why Ruby is sometimes considered to be in the Smalltalk lineage. The syntax has some superficial similarities, but the practical use of the language is more similar to PHP. Rails is extremely far from those dynamic Smalltalk application environments. Nothing is live. Object graphs are built up to serve a single request, then torn down immediately — a bizarre kind of kamikaze OOP. To me it's the worst of Smalltalk and PHP in one, as all the interesting aspects of dynamic typing are wasted and just become a source of bugs.
- jhgb 5y agoThe major similarities of Ruby and Smalltalk are semantic much more than syntactic (except perhaps for the existence of singleton classes). And as far as Rails is concerned, well, it probably wasn't written by a Smalltalker, but I fail to see how the existence of some specific framework changes how Ruby should be perceived as a language of its own.
- pavlov 5y agoI think most people would agree that the benefits of Smalltalk the language are inextricable from the runtime environment and GUI. Ruby has no such thing: it's pretty much only used for Rails and plain-jane Unix scripting. It's fair to judge the language in context of its actual applications.
- e12e 5y ago> I think most people would agree that the benefits of Smalltalk the language are inextricable from the runtime environment and GUI. Most, not all: https://www.gnu.org/software/smalltalk/manual/html_node/Overview.html#Overview https://www.gnu.org/software/smalltalk/manual/html_node/Over... Although it looks like somewhere along the path with the "new" graphical browser they dropped the tag line "Smalltalk for those who can type". Rails is a monster, and historically pretty poor ruby code quality INMHO. That said, ruby does indeed miss an "image" concept, but is quite dynamic and object oriented. Some smalltalk patterns would work well with ruby, I think. There's also (the abandoned?) maglev ruby on top of gemstone/s object db for smalltalk.
- setpatchaddress 5y agoI dunno what most people think about the benefits of Smalltalk, but I do know that people think Ruby and Objective-C are part of the Smalltalk lineage because they use the Smalltalk object model and have similar dynamic properties.
- jegea 5y agoRuby, the language, is almost as flexible and dynamic as Smalltalk. It's just that it didn't come with an integrated graphical environment like Smalltalk. For a glimpse of "what is possible", take a look at TkInspect (1), a set of gems that I'm working on that provide some of the goodies of that GUI, like an interactive, graphical console, a live inspector, a class browser or turtle graphics. At the moment it's not more than a toy, but it does definitely show what can be done. (1) https://github.com/josepegea/tk_inspect https://github.com/josepegea/tk_inspect
- Rochus 5y ago> initially Alan Kay tried to build something like Erlang It was actually Dan Ingalls who built it (btw. 15 years before Erlang was invented); he's also the author of the referenced worth reading paper; never understood why he didn't get the Turing price.
- bitwize 5y agoIndeed. Few people realize that Dan Ingalls was the John Carmack of the Smalltalk PARC team. Kay was the Romero.
- yesenadam 5y ago> Dan Ingalls was the John Carmack...Kay was the Romero. Sorry, I don't get the metaphor. It's a reference to a game I think?, but not sure which one, and I could be wrong. I'm very familiar with Ingalls and Kay, but not the other two, besides hearing Carmack's name around here sometimes.
- Pet_Ant 5y agoOn the off-chance this isn't a joke: https://en.wikipedia.org/wiki/Masters_of_Doom https://en.wikipedia.org/wiki/Masters_of_Doom
- yesenadam 5y agoOk thanks. No, it's not a joke. Don't know why you would think that. I'm getting strong signals here that Carmack/Romero are supposed to be a lot better known than Ingalls/Kay. Even though this is a Smalltalk discussion! (I've never been that much into computer games, besides occasionally writing them, and have always loathed "first-person shooter" games. Maybe that explains something.)
- bitwize 5y agoRomero was the "frontman" for Id Software (Wolfenstein, Doom, Quake) back in the 90s. He gave the magazine interviews, attracted the hype, and claimed much of the credit for the game's success, at least in the popular press. Carmack was the programmer who wrote the core bits that made the game possible. He didn't engage with the popular press, and when he did engage in discussions with the media or with fans, it was at a very deep and technical level. You may also think about it in terms of Wozniak and Jobs. Point being that Alan Kay was out there, engaging the press and talking about Smalltalk's big ideas (objects, messaging, computers as medium, how they relate to children, etc.). He was the frontman. Whereas Dan Ingalls deserves the bulk of the credit for actually writing Smalltalk. Fun fact: Ingalls wrote early Smalltalk versions... in BASIC.
- e12e 5y ago> Everything is inspectable, discoverable, interactive. Reactive programming, live objects, build stuff and see it come alive at every step. JIT makes everything fast, eventually. And yet we suffer the experience of web "apps" like Gmail, which have some similar properties (which I'm reminded of every time I hit shift-ctr-c rather than ctrl-c to copy something in office365/Outlook - and the dev tools pop up).
- igouy 5y ago> redefine "constants" like true by mistake No, really not by mistake — intentionally, because someone told you that it was possible and you wondered what that would break. > not sure how exactly did you end up with it during the interactive session Well, every change you made "during the interactive session" was logged as a sequence of Smalltalk change-set actions in the changes file. So, actually, you could just read what you did ;-) > Smalltalk … don't have much industry adoption… Now. Then: "Smalltalk, C++ knock heads. Computerworld 29, 45 (Nov. 6, 1995 ) https://books.google.com/books?id=oKDIlxbMaS4C&pg=PA153&lpg=PA153&dq=%22Smalltalk,+C%2B%2B+knock+heads+%22&source=bl&ots=WbagBcxHzo&sig=ACfU3U1-DIRvZ13ijiNqJANEwn0ifkibZQ&hl=en&sa=X&ved=2ahUKEwiStbKuj5_xAhVVgp4KHbJFBoMQ6AEwAXoECAIQAw#v=onepage&q=%22Smalltalk%2C%20C%2B%2B%20knock%20heads%20%22&f=true https://books.google.com/books?id=oKDIlxbMaS4C&pg=PA153&lpg=...
- nine_k 5y agoSurely, Smalltalk did have some adoption, and a huge influence! The JIT that made the JVM fast was adopted from Smalltalk! All the GUI stuff was heavily influenced by Smalltalk. Etc. But there were and are much fewer Smalltalk jobs in the industry than C++ jobs (though the Smalltalk jobs paid better). Much like there were more number-crunching C++ jobs than APL or k jobs, up until some key ideas of APL were made available wrapped in Python, and numpy jobs skyrocketed. Maybe something similar will happen to some key Smalltalk ideas!
- Rochus 5y ago> The JIT that made the JVM fast was adopted from Smalltalk No, that was technology developed for the Self programming language which didn't have much in common with ST (see e.g https://dl.acm.org/doi/10.1145/1238844.1238853 https://dl.acm.org/doi/10.1145/1238844.1238853, there is also an interesting talk by Ungar and Smith). The same technology was also used for an ST dialect (Strongtalk) which was quickly discontinued in favor of Java Hotspot. The influence of ST is generally overstated.
- e12e 5y ago> No, that was technology developed for the Self programming language which didn't have much in common with St (...) My understanding was always that self grew out of smalltalk? But I suppose the jit work in particular was developed for/in self? https://en.m.wikipedia.org/wiki/Self_(programming_language) https://en.m.wikipedia.org/wiki/Self_(programming_language)