$ cat hello.st
#!/usr/bin/gst
Transcript show: 'Hello World!'.
Transcript cr.
$ ./hello.st
Hello World!
$ du -b hello.st
64 hello.st
That's 64 bytes in a distributable unit. So, what's 50MB?Even combining the whole of the smalltalk package I used, it's only 18M:
$ du -bhc $(pacman -Qlq smalltalk | grep -v '/$') | tail -1
18M totalEdit
I should mention that shipping smalltalk applications generally means shipping the entire image. While there is work to make distributing just the code easier (EG. iceberg mentioned in the article) I don't believe this is yet a common practice. Even in that scenario however, you'll need an image to run that code and it will still be 50+MB.
Is that what Edward Diego meant?
Is Hello world what "smalltalk applications" generally means?
That's not the issue.
Not sensible is the issue.
What relevance does the distributable size of hello world have when the goal is to develop enterprise scale systems?
I think the most broadly applicable answer now is simply that including those development tools usually requires less-effort than not doing so.
That's a legacy from Smalltalk-80 application development at Xerox Special Information Systems (XSIS, back in the mid 1980s):
— "My response … is to remind the customer that the system is designed so that they can easily and freely change it. This concept is a new one to many people because traditional programming environments carefully protect system code from modification. The Smalltalk-80 environment treats system code and user code alike. Mold the system into an environment that suits your needs. The researchers designed the system so that they could experiment with creating new systems; the changeability of all of the system parts is a necessary attribute of this research."
p501 "Smalltalk - The Interactive Programming Environment", 1984.
Of course, some Smalltalk implementations did things differently:
- Dolphin Smalltalk could ship applications packaged as MSWin dlls
- Resilient Smalltalk used a completely separate Eclipse development environment to connect over TCP/IP to a VM+image embedded-system
What is the JVM equivalent ?