News for hackers. Stuff that matters.
Re:Smalltalk is not a perfect language. What are its shortco... by igouy on Friday November 01, 2019 @04:38PM (#21423460)
What is 50MB supposed to be the size-of ?

What is the JVM equivalent ?

Re:Smalltalk is not a perfect language. What are its shortco... by EdwardDiego on Friday November 01, 2019 @05:55PM (#21424109)
Let's say that the size we're measuring is the distributable unit. I give you this, and assuming you've got common dependencies, you can run it without building or compiling.
Re:Smalltalk is not a perfect language. What are its shortco... by jolmg on Friday November 01, 2019 @06:57PM (#21424582)
I only have a few minutes worth of knowledge of Smalltalk, but...

  $ 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 total
Re:Smalltalk is not a perfect language. What are its shortco... by epsilon_greedy on Friday November 01, 2019 @07:01PM (#21424604)
Gnu Smalltalk isn't used often (as far as I'm aware). If you use something more common like Pharo or Squeak, the base image includes things like the IDE, window environment, etc. and accounts for the 50MB size.

Edit

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.

Re:Smalltalk is not a perfect language. What are its shortco... by igouy on Friday November 01, 2019 @07:39PM (#21424834)
> … shipping smalltalk applications generally means …

Is that what Edward Diego meant?

Is Hello world what "smalltalk applications" generally means?

Re:Smalltalk is not a perfect language. What are its shortco... by epsilon_greedy on Friday November 01, 2019 @09:53PM (#21425387)
That is what I took "distributable unit" to mean, yes. Perhaps it's not fair to say that this is true for "hello world" as you've shown in your Visual Works example and jolmg has shown with GST.
Re:Smalltalk is not a perfect language. What are its shortco... by igouy on Sunday November 03, 2019 @12:43PM (#21435318)
> not fair

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?

Re:Smalltalk is not a perfect language. What are its shortco... by dpc_pw on Friday November 01, 2019 @07:17PM (#21424705)
It's like you shipped your shell, text editor, debugger and more with every program you made in Java. :D
Re:Smalltalk is not a perfect language. What are its shortco... by detaro on Sunday November 03, 2019 @12:45PM (#21435337)
Why would you ship those with a release of a smalltalk application?
Re:Smalltalk is not a perfect language. What are its shortco... by igouy on Sunday November 03, 2019 @09:36PM (#21438542)
Quite a good question.

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