7 ms·
Learning Smalltalk is not a waste of time
- shalabhc 9y agoThe article itself might be a fluff piece, but Smalltalk is a worthwhile investment of time anyway. I believe I grasped the more interesting ideas in Smalltalk when I approached it not as just another programming 'language', but rather as a complete programming 'system' in itself - a virtual computer, if you will. Instead of files, this system contains 'objects', which communicate with other objects via messaging. The entire network of objects is transparently persisted and implementation details are themselves represented as objects-with-messaging (i.e. self hosting). The UI is just another mechanism to send messages (clicks, keypresses) to some objects, etc. It's unfortunate that something like Unix with it's primitive notion of files, processes and 'stream of bytes' thinking has become the dominant environment, rather than something like Smalltalk - where the objects are reflective and communicate with semantically richer messages.
- lukego 9y agoI am writing Smalltalk code lately. I find it useful to think of Smalltalk as an operating system, like Linux or Windows or Emacs. It has a different way of doing things, and learning this is both frustrating and rewarding. It brings back vague memories of learning Linux for me. It feels like a nice way to break out of the bubble of that Rob Pike famously lamented in http://herpolhode.com/rob/utah2000.pdf http://herpolhode.com/rob/utah2000.pdf.
- shalabhc 9y agoYes the analogy to an OS is good. Many language comparisons sadly miss this because they just look at Smalltalk through a 'programming language' lens and only see at a slice of the Smalltalk system. Interestingly there is an Pharonos project (maybe defunct now?) http://pillarhub.pharocloud.com/hub/mikefilonov/pharonos http://pillarhub.pharocloud.com/hub/mikefilonov/pharonos
- banachtarski 9y agoI can't help but feel there's sort of a strawman here. I'm not sure what social circles the OP hangs out in, but I don't imagine anyone I know would really lambaste my choice of language to learn in my fair time (or even as my first language). That said, I think I differ in terms of what I believe a language offers, and given the criteria prescribed in the article, smalltalk is actually probably not a good choice. For example: > Your first programming language will never be your only programming language Yes, but for a first language, isn't it more pragmatic to learn a language at the intersection of more popular languages? If you knew you were likely to want to speak English, French, and Italian, would you really opt to start with, say, Swahili or Korean? > The best way to learn how to program is with a good teaching language. His argument here doesn't make much sense. I think a "good teaching language" is less about the language and more about the availability of teaching material. The language semantics are trivial to pick up once you have a good foundation, so why not focus on the foundation (and not the language), and pivot as you like afterwards? > There is no better way to learn about object-oriented programming (OOP). I'm going to call shenanigans on this one. Learning good OO design isn't going to magically come as a consequence of learning _any_ language, and smalltalk being the paragon (supposedly) is a silly notion. Tons of languages have delivered new paradigms as a result. By this argument, we should just learn every language as our "first" language to learn concurrent/functional/low-level/etc concepts best > It’s a great hobbyist language. It depends on your hobby! If you like making console games, uhhh you're shit out of luck with small talk aren't you. Or what if you enjoy experimenting with large datasets. Do you really want to work with a smalltalk-to-tensor flow API? For the record, I'm not saying OP can't learn smalltalk. Just that in being defensive, it's not good to pendulum to prescriptivism.
- fractallyte 9y agoSmalltalk is more akin to Latin, which is a fine choice for learning the foundation of European languages. Its simple syntax, within a logical and consistent language, makes it (in my opinion) the best way to pick up OO concepts. Being highly 'visual' is definitely an advantage that very few other languages can offer.
- banachtarski 9y ago
- mburney 9y agoI thought that Python is designed to be a teaching language.
- fractallyte 9y agoPython has all the hype and popularity, but Smalltalk, Pyret, and Racket are far better choices.
- r00fus 9y agoAs a Smalltalk dev for a couple of years, I feel my biggest moments of enlightenment were not with Smalltalk, but Scheme (i.e., Lisp) and (yes, not a popular opinion) Javascript (Prototype-based language that eschewed rigid class hierarchies). I still love Smalltalk but it's elegance (message passing FTW) and purity set a bar too high for me, and it still fell afoul of the fact that class hierarchies create a syntax/behavior that require you to re-learn a lot every time you join a new project (too many companies/projects rewired basic class functionality).
- eesmith 9y agoABC was designed as a teaching language. Guido van Rossum was an implementer (but not designer) of the ABC language. When he started Python, he included ideas in it which came from ABC.
- _ph_ 9y agoIn my eyes, there is a small group of languages everyone should get familiar with, who wants to understand the fundamental programming principles. It also makes one understand how other language support those principles and how to best use them. Smalltalk certainly belongs to that group of languages (others would be Scheme/Common Lisp). Smalltalk is the fundamental OOP language. Everything is an object. Classes, numbers, booleans, all can have methods. Actually another interesting property of Smalltalk is, that constructs like if/then or for loops are just methods on the boolean and integer classes respectively. Being dynamically typed, Smalltalk also does not force you into inheritance just to satisfy a type signature. Java got that almost right with the interfaces, unfortunately too many libraries rather require you to inherit from a base class instead of implementing an interface - Go put that to extremes by only offering interfaces but no inheritance. Finally, Smalltalk is always integrated into some sort of IDE and class/object browser, mostly doing image-based development. So, even if one is never going to do a larger project in Smalltalk, I can only recommend getting familiar with Smalltalk and its concepts, it changes the way how one thinks about OOP in other languages too.
- ungzd 9y ago"Image" system might be too alien, this approach is very specific to Smalltalk. And when I tried to learn Pharo (which is probably implementation of smalltalk best for learning today) I had impression that documentation is not very good, and there are few good tutorials. There are some big and serious books, there is Pharo MOOC, everything is so serious and academic that gives impression that the language is hard. There's no simple stupid tutorial like in other languages.
- nyankosensei 9y agoIf you download and run Pharo, a Welcome screen appears with a menu that includes “Learn Pharo Smalltalk”. That leads to a simple interactive tutorial called ProfStef that introduces you to Smalltalk syntax. There’s also a link to a free introductory book called “Pharo by Example”.
- b0rsuk 9y agoCan someone give me a concise explanation why a language this influential and talked about is not used for regular programming ? What are its disadvantages ?
- orbz 9y agoThere's always been a bit of debate around this but it usually comes down to the combination that the major implementations of Smalltalk were commercial and development was image based as opposed to flat file based.
- pliftkl 9y agoSmalltalk as a language is small ("fits on a postcard"), and anyone can implement this. However, to be usable, smalltalk really needs to live in a full featured IDE. Full featured IDE in the 90's meant expensive software from vendors, and the limited pool of developers made development expensive. Had Pharo come around 30 years earlier, we might have seen a very different result.
- flavio81 9y ago>Can someone give me a concise explanation why a language this influential and talked about is not used for regular programming ? Back in the late 70s and early 80s, to use it you required a system with very big memory and fast processor speed (read: an expensive workstation), and the implementations/compilers were mostly propietary and expensive as well. Same reasons Lisp isn't more popular. >What are its disadvantages? There are really no disadvantages to Smalltalk. Although personally i'm not so comfortable with a language that only allows message-passing OOP as its paradigm; and Smalltalk is not the highest performing of languages. OTOH Smalltalk, in 2017, should run substantially faster than some other popular, well-liked programming languages such as Ruby.
- todd8 9y agoBasically, programming language paradigms evolve and new languages are developed. Smalltalk was influential, but new languages have moved in and taken over the space where Smalltalk might have been used otherwise. I saw Smalltalk running on the Xerox Alto while in an advanced programming language group at Texas Instruments around 1978. Having some background in object oriented programming (from studying Simula-67 and working with MIT's CLU programming language) I was eager to read the excellent Smalltalk-80 books published a few years later. I actually got to use Smalltalk on my own PC when Digitalk came out with Smalltalk/V that ran on MS-DOS around 1986. I liked Smalltalk enough that I considered using it as the basis for a large commercial application I was designing in 1990, but ultimately I decided not to incorporate it in our system for a number of reasons. Smalltalk is talked about because its design and implementation are very elegant. However, it was designed around the idea of a single user environment supporting a custom GUI architecture. Source code wasn't stored and loaded from files, instead a system image was maintained and each time Smalltalk was started the current state was loaded and started running. The runtime, editor, debugger, even the GUI itself were a part of this image and subject to change as as application was being developed. It was a system seemingly designed for a computer with one programmer working on one program. This fluidity made working with the system fun and productive for a single programmer, but it wasn't obvious how it scaled up to larger multi-programmer projects. Furthermore, it was interpreted and that hurt back then when computers were much slower. Also, it's GUI graphics was designed around simple bitmapped black & white hardware, no grey scale or color. Again it wasn't obvious how this was supposed to work on different hardware. These limitations have a lot to do with the history and original limitations of the early systems that Smalltalk ran on, not the language; nevertheless, like other early interesting and seminal programming languages (APL for example) its best ideas were incorporated in future programming languages. The so-called "message-passing" paradigm of Smalltalk can be seen in Objective-C. It's implementation of classes as manipulatable objects themselves with their own meta-classes is seen in Ruby and Python and Common Lisp meta-programming. C and Pascal were contemporaries of Smalltalk and were both quite successful and influential. They had simpler, file based models for programs. Most systems used punched cards or simple CRT based terminals for construction of programs. This worked much better for C and Pascal than Smalltalk a language made for use with a GUI. Smalltalk was an early object oriented language, but it wasn't the first. Simula-67 was the first object oriented language and these ideas were further explored by MIT's CLU. At this time O-O ideas in programming were being explored, and this led to the evolutionary development of MODULA (from Pascal), C++ (from Simula67, Algol68, CLU), and Objective-C (from Smalltalk and C) and Ada (from many sources). At the time, I liked the simplicity of Objective-C, but C++ had the important backing of AT&T, was the most efficient implementation of object-oriented ideas, and came out the winner. C++ was complex being hampered by compatibility with C semantics; this gave Java an opening to become the other important Object Oriented language Other important developments in programming languages were taking place while this was happening. Lisp (the second oldest programming language in wide use) was splintering into numerous dialects. This was addressed by taking the union of the best ideas and Common Lisp came into being. A reaction to this large language was a small elegant Lisp called Scheme (perhaps the intersection of the best ideas in other Lisps). Object oriented ideas were incorporated in Common Lisp, but a new programming paradigm grew out of Lisp: functional programming exemplified by ML and its derivatives SML and OCaml, Haskell (influenced by Scheme), and their newer offspring: Rust, Swift, and Scala. These and many other further developments in programming languages, sadly, leave little room for a rebirth of Smalltalk.
- eesmith 9y ago"Old languages still have great value" The author picked only those old language which still have great value. The author did not include such languages as Algol, JOVIAL, MUMPS, SNOBOL, or TRAC. There are a lot of old languages with little modern value. (Then again, a lot of new languages have little value.) Since the author did not include COBOL, should I infer that "great value" doesn't include "getting a job developing legacy systems"?
- coldtea 9y agoWhat the author tried to convey by "old languages still have great value" is that: "Old languages shouldn't be discarded as valueless just because they're old. Some old languages have great value". And not: "Any old language still has great value". https://en.wikipedia.org/wiki/Principle_of_charity https://en.wikipedia.org/wiki/Principle_of_charity
- eesmith 9y agoPoint taken. I think, however, that it's at least somewhat of a strawman argument. The argument is "Why learning Smalltalk can never be a waste of time" and #6 is "Old languages still have great value", concluding that "When did “old” ever become a liability, as many opine?" But how many people really say that Smalltalk is a waste of time because it's an old language? My experience is that it's not a common argument against learning Smalltalk. That said, I also object to the use of the starting dates as the date for the language when, for example, the C language from the 1970s is not "very commonly used for systems programming" - at the very least that should be ANSI C. Similarly, I know it's not useful to study the Python of its first release for anything other than historical interest. For one, the __init__ convention hadn't yet been created, so objects were initialized manually.
- coldtea 9y ago>But how many people really say that Smalltalk is a waste of time because it's an old language? I think a lot of people in the industry, especially younger ones in startups and fad-driven cultures, tend to discard older languages with similar criteria. Not just Smalltalk, even something like Java -- "people still use that?".
- cztomsik 9y agoI wonder if anyone would agree with me but my experience with (Smalltalk way of) OOP is that it's extremely powerful and expressive but very hard to follow (thanks to messaging). Like in ruby, you can code "in english" but once you're trying to find a bug, it's not easy to tell what is and is not possible to happen, you just have to run it and see where it dies. This is to some extent similar to macros. They are also very powerful but should be used sparingly. It's definitely great experience (I especially like the fact that what you see in browser is not code but actual object memory which get serialized to string) but you should be warned that this is not probably a good fit for production applications done by bigger teams.
- flavio81 9y agoAnother Smalltalk article from the same author ("Richard Kenneth Eng"). He has at least three articles where he considers Smalltalk the best language ever, while simultaneously bashing Common Lisp (& other languages), with claims that show his knowledge of CL is not even superficial. Plus ignoring that the creator of Smalltalk, Alan Kay, is a fan of Lisp himself and on the early 70s these two were the main languages for OOP and had mutual influence. Not to mention that the early alma mater of Smalltalk, Xerox PARC, was also a center of innovation for Lisp as well. No problem at all promoting Smalltalk, but when articles are just clickbait-y and have claims with no technical substance, they become articles for their own sake.
- deleted 9y ago[deleted]