4 ms·
> the benefits of having a full-fledged Smalltalk VM are immediately visible. I'm not so sure they are. I've personally never been able to wrap my head around
by sanderjd 11y ago
> the benefits of having a full-fledged Smalltalk VM are immediately visible.
I'm not so sure they are. I've personally never been able to wrap my head around how I would use any of the Smalltalk environments I've played with to create and distribute something useful to a real person, entirely due to the necessity of "a full-fledged Smalltalk VM". It seems too all-or-nothing; maybe it would work well as an entire OS, but it doesn't work great at the application level.
- AceJohnny2 11y agoFrom trying multiple times to give Smalltalk a spin, this has been my thought as well. It has a bootstrap problem, where it's hard to integrate it with the rest of the software ecosystem. I'm sure there are solutions to that, but they aren't advertized as well.
- pjmlp 11y agoYou could generate an executable with a pruned image. At least with the commercial Smalltalks.
- xrange 11y agoCan anyone tell us how cumbersome it is to do the same thing with the free Smalltalks?
- david-given 11y agoGNU Smalltalk is script based and while it's got support for images you don't have to use it if you don't want to. You can write a viable program by just creating a script with #!/usr/bin/gst at the top. It also comes with Seaside, which is a pretty nice web app framework, and will run out of the box. Instructions here: http://smalltalk.gnu.org/blog/bonzinip/seaside-development-gnu-smalltalk http://smalltalk.gnu.org/blog/bonzinip/seaside-development-g...
- sanderjd 11y agoNeat, thanks for the pointer. Can you speak to what another commenter said about GNU Smalltalk being a not-particularly-great implementation?
- david-given 11y agoAll I have is anecdata, and stale anecdata to boot, so it would just be misinformation. I do see that the last release was two years ago, though.
- deleted 11y ago[deleted]
- pjmlp 11y agoSince I cannot edit my comment any longer. For example, this is how VisualWorks Smalltalk does it (Application Delivery chapter): www.cincomsmalltalk.com/main/Documentation/VisualWorks/AppDevGuide.pdf
- BuildTheRobots 11y ago(stupid question; I know nothing about smalltalk, but:) the necessity for a "fully fledged VM" doesn't seem to have slowed down Java adoption. Could you enlighten me as to how/why I've entirely missed the point please? :)
- david-given 11y agoThe Java VM is like a virtual processor --- it lets you run an ordinary program that's written in Java bytecode. The Smalltalk VM is like a machine emulator --- it runs a complete Smalltalk system, complete with its own screen, GUI, multiple processes and concurrent programs, IDE, debugger, editor, etc, all mixed together. This typically all runs inside a single window, with its own windowing system. It's a hangover from the days when Smalltalk would run on the bare metal of a computer --- it was the entire operating system.
- igouy 11y agoYou seem to have confused the Smalltalk VM with the Smalltalk image. Most Smalltalk implementations have 4 pieces: - VM like the JVM - sources file - changes file - image file No it does not "typically all run inside a single window, with its own windowing system".
- sanderjd 11y agoYeah, to say the same basic thing as the other commenter, but to use a different analogy, the "fully fledged VM" of Smalltalk is (or has been, in my experience) more like running a different OS in a VirtualBox window than like running a Java program. I think the JVM is a bit misleadingly named, or at least uses the VM terminology in a different way; it's really "just" an interpreter for a fairly simple assembly-ish language with a large runtime.
- david-given 11y agoI'd have to agree. I have never wanted to write a program that would run inside a Smalltalk environment. I have never wanted to use a Smalltalk environment --- every time I've tried one I end up ragequitting after a few minutes because of the ghastly nested windowing system. And I love Smalltalk, as a language. I want to write programs in it, and use it more, and get stuff done in it, but I'll be damned if I'll fight Squeak's windowing system and bizarre VCS. Right now the only way I have to run Smalltalk is via Gnu Smalltalk, which is a bit old and cranky and not very fast. This makes me very sad. (I wonder if I could translate Smalltalk source in to Lua and push it through LuaJIT...)
- ljw1001 11y agoDear god, don't use Squeak. Pharo.
- igouy 11y agoYou seem to have confused the Smalltalk VM with the Smalltalk image. Most Smalltalk implementations have 4 pieces: - VM like the JVM - sources file - changes file - image file
- sanderjd 11y agoTo quote myself: > I've personally never been able to wrap my head around how I would use any of the Smalltalk environments I've played with to create and distribute something useful to a real person I'm not confused about the existence of different pieces, I've just never been able to wrap my head around how to fit everything together within the current software ecosystem to create and distribute something useful to a real person. This may be due to any number of things: poor intelligence or research on my part, poor marketing on the part of the smalltalk community, poor documentation, or a design that just doesn't fit in very well. I'm not at all convinced it can't be done, I've just never been able to figure it out. I'd really love to read an article along the lines of, "here's how we successfully created and deployed a non-trivial smalltalk application sometime within the last 5 years".
- igouy 11y ago>>…how to fit everything together within the current software ecosystem…<< You mean like using Win32™ DLLs? http://www.object-arts.com/downloads/docs/parameterconversionandwrappermethods.htm http://www.object-arts.com/downloads/docs/parameterconversio... I haven't been looking for Smalltalk success stories. This sort-of thing? http://pharo.org/success http://pharo.org/success
- igouy 11y ago>>but it doesn't work great at the application level.<< And yet -- A very large Smalltalk application was developed at Cargill to support the operation of grain elevators and the associated commodity trading activities. The Smalltalk client application has 385 windows and over 5,000 classes. About 2,000 classes in this application interacted with an early (circa 1993) data access framework. The framework dynamically performed a mapping of object attributes to data table columns. Analysis showed that although dynamic look up consumed 40% of the client execution time, it was unnecessary. A new data layer interface was developed that required the business class to provide the object attribute to column mapping in an explicitly coded method. Testing showed that this interface was orders of magnitude faster. The issue was how to change the 2,100 business class users of the data layer. A large application under development cannot freeze code while a transformation of an interface is constructed and tested. We had to construct and test the transformations in a parallel branch of the code repository from the main development stream. When the transformation was fully tested, then it was applied to the main code stream in a single operation. Less than 35 bugs were found in the 17,100 changes. All of the bugs were quickly resolved in a three-week period. If the changes were done manually we estimate that it would have taken 8,500 hours, compared with 235 hours to develop the transformation rules. The task was completed in 3% of the expected time by using Rewrite Rules. This is an improvement by a factor of 36. http://portal.acm.org/citation.cfm?id=604258 http://portal.acm.org/citation.cfm?id=604258
- deleted 11y ago[deleted]
- mark_l_watson 11y agoHow about writing web apps in Pharo (or Squeak)? There are several nice frameworks, Seaside just being on of them.
- coldtea 11y agoHow is it any different than requiring a runtime (e.g. Java or NET)? That you also distribute the image? That's not that big a difference distribution-wise.
- justaaron 11y agodepends upon your definition of application... a machine-consuming set of processes working together, possibly across a distributed network? ummm yeah perfect. smalltalk, erlang, and a handful of other candidates... Java would be considered "experimental" in such environments, as supervisory trees etc are not inherent. building "apps" for desktop or mobile? ok, you got me there... smalltalk is probably not apropo...
- igouy 11y ago>>building "apps" for desktop or mobile? ok, you got me there... smalltalk is probably not apropo...<< … because?