13 ms·
I very much agree with this. The way that Smalltalk is typically implemented (VM/OS) solves some very tricky problems that almost nobody has. Taking for exampl
by zamalek 11y ago
I very much agree with this. The way that Smalltalk is typically implemented (VM/OS) solves some very tricky problems that almost nobody has.
Taking for example the main solution that it features: allowing for portability by running everything inside of a VM. This is an incredibly smart idea, however, it results in apps that don't 'glue' well with the actual OS. Furthermore, even the worst-case language for portability, C, does a pretty damned good job at being portable if the developer is disciplined.
On the fly editing? Awesome idea, really smart. Just don't go anywhere near my production servers with live editing.
That's what Smalltalk is to me: a bag of really smart ideas that nobody ever asked for in the first place. Really, ObjC is what Smalltalk could have been had the word "no" been used more frequently. It's a good example of what happens if someone doesn't realize that "less is more."
- lispm 11y ago> allowing for portability by running everything inside of a VM like Java Btw., it's Smalltalk, not SmallTalk.
- dkersten 11y agoAnd .NET/Mono, Ruby, Python, Javascript, etc etc.
- zamalek 11y agoThe Java way of VM is not the Smalltalk way of VM :). "VM" has become quite an ambiguous term - the Smalltalk VM is closer to (not exactly like) a Xen/VMWare-like VM: Smalltalk avoids the OS by having its own "OS." Java/.Net/etc. VM is what I (and some others) call a "runtime environment." These are far simpler than what Smalltalk provides (e.g. you don't mess about with images), once again, likely as a result of someone holding back from blue sky architecture.