7 ms·
In which we plot an escape from the quagmire of equality (Clojure and Emacs)
- AlexFromBelgium 15y agoI keep reading how amazing smalltalk, and it's development environment used to be... Why did we lose it? Was it companies trying to 'dumb down' programming (java..?). Tell me, what happened?
- locopati 15y agoFor one, it cost a lot of money so it had a limited audience. Afaik, VisualStudio drew a lot of inspiration from it, which propagated outwards to the Java IDEs.
- ConstantineXVI 15y agoFWIW, Visual_Age_ (not to be confused with VS), the ancestor to Eclipse, was originally Smalltalk based before being rewritten in Java.
- technomancy 15y agoAlso working in terms of an image instead of files freaks people out. It isolates you from all the file-centric tooling of unix.
- AlexFromBelgium 15y agoThx for the responses. I just watched "What Killed Smalltalk Could Kill Ruby, Too" http://www.youtube.com/watch?v=YX3iRjKj7C0 http://www.youtube.com/watch?v=YX3iRjKj7C0 pretty interesting
- rjsamson 15y agoThis is something I'd like to hear more about too - if Smalltalk is so awesome, why is nobody using it?
- gruseom 15y agoWith programming languages, I've come to the conclusion that "If X is so awesome, why is nobody using it?" is the wrong question to ask. Or rather, it's a fair question, but the answer doesn't depend on X. It is overwhelmingly a matter of network effects and social proof. What matters is what everyone else is using. A programming language has a window of opportunity to gain mindshare while it's new. Once that window passes, the odds are hugely against it. It's true there are a few technical factors, for example that older implementations lack the infrastructure to work with newer technologies, but such things can be improved. The dominant factor, the real barrier, is social psychology. This is obscured by our tendency to retrofit plausible-sounding reasons to our choices ("X is slow" or "it doesn't have libraries" or whatever). This does suggest a strategy for reviving an old language: rebranding. First, you need a new implementation. Trying to convince people to use the old one is like trying to get them to watch an old movie. George Lucas didn't promote Kurosawa, he made Star Wars. Second, there has to be a hook, something to convince us that this really is a new language, modern and with the times. So, light sabers. That's critical for opening a fresh window of opportunity instead of getting pegged to the old, long-closed one. It needn't be the most important thing, but it can't be fake either; it must be real enough or no one will take the new brand seriously. Without a convincing reason for why we weren't using X before, the new window will never open. Once it opens, then and only then do the beauty and power of X get their chance to bond with the user. In the Star Wars analogy, that would be the characters and the story – the deeper things that came from Kurosawa and ultimately from ancient archetypes. They'd never have gotten the chance to kick in if Star Wars hadn't got the audience in the theater. Once they did, though, then you had Star Wars fans for life. With Clojure, the hook was Java libraries. Actually, there were three hooks. The others were concurrency and sequences. But Java libraries is the one that worked. And now there's a modern Lisp again!
- deleted 15y ago[deleted]
- fractallyte 15y agoHerd mentality? It's the only explanation that fits the facts... If you're pursuing a programming language/environment because it's fashionable, you're doing it wrong.
- gruseom 15y agoAs I understand the story from old Smalltalkers, the Smalltalk vendors shot themselves in the foot and then the head. They had exorbitant licensing schemes where Java was free, didn't make it easy for programmers to try Smalltalk out, and had a supercilious "we're the best, bow before us" attitude that extended into the technology itself, making interop harder than it needed to be and so on. The same attitude caused them to look down their noses at Java and C++ – after all, Smalltalk was obviously better – until it was too late. Given how much better Smalltalk was than Java and how much of a head start it had, it should have won. That it didn't is either a tragedy or a comedy. Edit: Part of the issue was generational. Smalltalk predates open-source. So do APL and Lisp. The way people thought about commercial software before open-source was totally different. For example, it wasn't uncommon for vendors to demand a percentage of their users' revenue, something that seems absurd today. So these technologically advanced – still in many ways superior – languages were trapped for historical reasons in an obsolete economics.
- javajosh 15y agoThis kind of begs the question: now that we know all this, why aren't these technologies being resurrected and offered again with better economics? (The only reason I can think of is that the IP is still being controlled by those who remain to this day, blind.)
- gruseom 15y agoWe don't know all this. (See my other comment in the thread for a lengthier attempt at explaining.)
- javajosh 15y agoDo you mean http://news.ycombinator.com/item?id=3900047 http://news.ycombinator.com/item?id=3900047 ? I actually disagree strongly with you there. Hackers are eager to find things that work better, regardless of their source. One example that springs to mind is the use, in 3D graphics programs, of an archaic math construct called the 'quaternion'. The quaternion was the loser in a long-ago war with 'vectors', but this did not stop hackers from using the idea with the most value. Another more ready example (as evinced by the frequent posts on HN about it) is Emacs. It's an old editor. And yet it still has it's adherents, and new converts. But I hear nothing about people making anything in smalltalk environments. Nothing. Not even toys. One would think that if the language/environment was so powerful and the software freely available, that we would have seen something built on it. Heck, erlang is pretty esoteric (especially to those who don't hang out around here) but someone built CouchDB on erlang (and then abandoned it, but that's another story :). In summary, I think there might be something wrong with Smalltalk that has nothing to do with economics.
- bsiemon 15y agoIn it's heyday smalltalk VM performance was far behind C,asm,etc. As a result it never gained much traction. Once it became practical to run/use VMs the smalltalk legacy had been tainted by C/C++ and thus java.
- dyeje 15y agoIs the font on this page really hard on the eyes or is it just me?
- groovy2shoes 15y ago> As it comes from a Scheme background, Guile provides > the immutable data types we need. Scheme does not provide any immutable data types beyond numbers or symbols, either. Procedures like `set-car!`, `vector-set!`, and `string-set!` all modify their operands. In fact, in R5RS, there's no real way to introduce truly disjoint types (you can, however, simulate them as in SRFI-9 which is being incorporated in R7RS), so it'll be a little difficult to even introduce new types let alone interoperable new types. > One of the Summer of Code projects for this year is > to allow for pluggable backends in the ClojureScript > compiler, with Lua as a proof of concept. Compound data types in Lua are similarly mutable (perhaps even more so because mutation of tables is acceptable practice in Lua). There will be difficulties targeting ClojureScript to Lua, too. > Of course, with a compiler that targets Emacs Lisp, > you can work around this by implementing your own > immutable types. But this makes any form of interop > much more cumbersome... you have to choose between > getting equality right and seamless interop. It's just a fact of life that when introducing a radically different paradigm to any language platform, interop is going to have seams. [EDIT - formatting]
- technomancy 15y agoThanks for the pointer. Guile does in fact have immutable strings and lists, but apparently they do not actually come from the Scheme standard: http://lists.gnu.org/archive/html/guile-devel/2012-01/msg00135.html http://lists.gnu.org/archive/html/guile-devel/2012-01/msg001.... I will update my post to reflect this. I'll keep a close eye on the Lua ClojureScript backend as well; this should be interesting.