Skip to main content

Smalltalk Challenge: Post 2 - Switching to Squeak

A quick survey of Smalltalk's keywords, constructs, and syntax isn't enough to understand how the language approaches programming. There is only a handful of keywords, no control structures, and the syntax is quirky in spots but is hardly exotic. To really get an appreciation, it's helpful to place the language in its historical context. Smalltalk wasn't intended to be a general purpose systems programming language like C, rather it was designed to allow ordinary people to take full advantage of their computers and to be easy enough for children to learn. The intended environment was immersive, interactive, and most-importantly visual. Smalltalk was more than a programming language, it was an entire operating environment.

Xerox was working on the Dynabook at its Palo Alto Research Center in the early 1970's. The Dynabook was to have many features we now see in personal laptops and tablet devices (such as touch screens, mice, windowed display managers, etc.). Alan Kay argued that existing languages were ill-suited and a new programming language was necessary for the end-user to realize the full potential of the system. He drew inspiration from the work of Jean Piaget and others in developmental psychology and constructionist learning, which set the direction of Smalltalk. The Dynabook project never came to fruition, but Smalltalk lives on, and both had a lasting influence on computing that we still see today.

Given this background, I suspected something like Squeak would really be better suited for learning Smalltalk as it was intended since Squeak is the modern implementation of the language and environment that was developed at Palo Alto. I asked Josh if it was okay to switch from GNU Smalltalk to Squeak. He agreed-- admitting that he only proposed GNU Smalltalk because it's what he already had on his system from Portage. I checked apt and was amazed to find Squeak in Ubuntu's repositories (with bets on the MotU pulling it without telling anyone within the next two releases). After running sudo apt-get install squeak-vm and starting Squeak, I was staring at a pretty gaudy looking graphical environment.

I took the liberty of running a "Hello World" program. The System Browser window is at the top, a Workspace window is in the middle, the Transcript window is at the bottom, and the Objects Library window is to the right. I entered the statement Transcript show: 'Hello World!' in the Workspace, highlighted it, and chose "do it" from the popup menu.

Every element is an object which you interact with by sending it messages. In the above example for instance, I interacted with the Transcript window by sending it the show: message and the argument 'Hello World!'. The window responded by displaying the text.

I did a screen recording of another example to help give you a better idea what interaction in the graphical environment can look like. I placed a Star object on the world (the main "desktop" area) and used its Inspection window to send the messages borderWidth: and rotationDegrees:. The object responded by redrawing itself with a thicker border and different rotation.

Have you been challenged to learn a new language, or have you been learning/working with Smalltalk? Feel free to leave your comments about it below.

Labels:

Comments

Post a Comment

Popular posts from this blog

Writing a Minimal PSR-0 Autoloader

An excellent overview of autoloading in PHP and the PSR-0 standard was written by Hari K T over at PHPMaster.com , and it's definitely worth the read. But maybe you don't like some of the bloated, heavier autoloader offerings provided by various PHP frameworks, or maybe you just like to roll your own solutions. Is it possible to roll your own minimal loader and still be compliant? First, let's look at what PSR-0 mandates, taken directly from the standards document on GitHub : A fully-qualified namespace and class must have the following structure \<Vendor Name>\(<Namespace>\)*<Class Name> Each namespace must have a top-level namespace ("Vendor Name"). Each namespace can have as many sub-namespaces as it wishes. Each namespace separator is converted to a DIRECTORY_SEPARATOR when loading from the file system. Each "_" character in the CLASS NAME is converted to a DIRECTORY_SEPARATOR . The "_" character has no special
6 comments
Read more

Composing Music with PHP

I’m not an expert on probability theory, artificial intelligence, and machine learning. And even my Music 201 class from years ago has been long forgotten. But if you’ll indulge me for the next 10 minutes, I think you’ll find that even just a little knowledge can yield impressive results if creatively woven together. I’d like to share with you how to teach PHP to compose music. Here’s an example: You’re looking at a melody generated by PHP. It’s not the most memorable, but it’s not unpleasant either. And surprisingly, the code to generate such sequences is rather brief. So what’s going on? The script calculates a probability map of melodic intervals and applies a Markov process to generate a new sequence. In friendlier terms, musical data is analyzed by a script to learn which intervals make up pleasing melodies. It then creates a new composition by selecting pitches based on the possibilities it’s observed. . Standing on Shoulders Composition doesn’t happen in a vacuum. Bach wa
7 comments
Read more

Learning Prolog

I'm not quite sure exactly I was searching for, but somehow I serendipitously stumbled upon the site learnprolognow.org a few months ago. It's the home for an introductory Prolog programming course. Logic programming offers an interesting way to think about your problems; I've been doing so much procedural and object-oriented programming in the past decade that it really took effort to think at a higher level! I found the most interesting features to be definite clause grammars (DCG), and unification. Difference lists are very powerful and Prolog's DCG syntax makes it easy to work with them. Specifying a grammar such as: s(s(NP,VP)) --> np(NP,X,Y,subject), vp(VP,X,Y). np(np(DET,NBAR,PP),X,Y,_) --> det(DET,X), nbar(NBAR,X,Y), pp(PP). np(np(DET,NBAR),X,Y,_) --> det(DET,X), nbar(NBAR,X,Y). np(np(PRO),X,Y,Z) --> pro(PRO,X,Y,Z). vp(vp(V),X,Y) --> v(V,X,Y). vp(vp(V,NP),X,Y) --> v(V,X,Y), np(NP,_,_,object). nbar(nbar(JP),X,3) --> jp(JP,X). pp(pp(PREP,N
22 comments
Read more