7 ms·
Travels with Smalltalk (1995)
- ngcc_hk 8y agoStill relevant today? In 1988, I was briefed by Ibm how they would use Smalltalk with about 10 programmer develop something to ... do not believe them for 1s. What is the business model is then what Microsoft teach the world. It is not technology but the business (the share to the inventor and investor) or later in 1990s (we learn from open sources) the governance and partipation model that rule. Also, it is dynamic and environment base then, how to work in a large team is not that resolve for new firm to use it. Hence once again a 2018 to 1998 me, is this still relevant. I read this btw during my 15min search about this and give up. Like 1988. https://medium.com/@richardeng/mobile-smalltalk-c6f0cc712909 https://medium.com/@richardeng/mobile-smalltalk-c6f0cc712909
- em-bee 8y agoi am struggeling to understand what you are trying to say. could you please elaborate? what is it that you don't believe about IBM? and what is your point about large teams and new firms? here are my thoughts: if you didn't think smalltalk was useful in 1988 then you probably won't feel any different today. i feel today that smalltalk is interesting. in 1988 it would have blown my mind. here is why: today most languages in use fall into two major groups: lower level languages like C and C++ where you do your own memory management, etc. and higher level languages that use some form of runtime and do a lot of work for you. when i was studying in the early 90s, i felt that the latter group of languages were not taken seriously. they were called scripting languages and were more or less only useful for toy programs. (i know that is wrong, but that is what i was led to believe). today these so called toy languages are growing and growing and they are slowly pushing C/C++ and related languages to the side. we get more and new variants of these languages every year. but, and that is the kicker: hardly any of these languages add something that smalltalk (and lisp) didn't already have. we keep reinventing the syntax, but we are not actually changing how we program computers. exceptions are few and far between. additionally, smalltalk (and lisp) achieve the same with a minimalist and thus much easier to learn syntax, so that since learning those two languages, almost all others feel like a step backwards. this is what makes smalltalk relevant today. smalltalk and lisp act like a high-water-mark, as a reminder that most of the languages we are using today don't float our boat any higher than it did 50 years ago.
- gaius 8y agoIt’s no mystery. In the early-mid 90s IBM was ramping up on Smalltalk believing it to be the language of the future enterprise. In the late 90s they realised that jumping on the Java bandwagon would be more profitable so they ditched Smalltalk almost overnight. The same reason IBM does anything, including Linux.
- imglorp 8y agoI know a guy that worked for IBM writing a large bunch of UI in Smalltalk (80?), desktop of course, on OS/2. He was highly supportive of the productivity and environment, but business concerns pushed them in another direction.
- EdwardCoffin 8y agoAs I understand your comment, you are saying: 1) thirty years ago you were given a sales pitch about Smalltalk that you disbelieved 2) You don't know how to make it work with a large team 3) That you gave up reading an article that is written for an audience of Smalltalk programmers on how to handle a particular situation, despite you yourself presumably not being a Smalltalk programmer How is any of this relevant?
- geocar 8y agoInside a mildew-covered Tudor barn, and primed with much whiskey, Dave Thomas convinced me that the Open Source Movement was bad for invention and progress: Where it may do good, it also robbed developers of the opportunity to be paid fairly for their work, and that was bad. Once upon a time, you could make a piece of software and sell it for $1m, but now you are competing with someone who would take a little "free software" and sell their consulting on top of it. You may be able to take pride in the quality of your work, but that consultant can't afford to so he won't. And things get worse. If you sell a piece of popular software to many people for $100 each you could still make a lot of money, but how does your consultant fit into this? You're still competing with him, and he's willing to build on top of someone elses' work to do so. He's not delivering $100 worth of value (and doesn't charge that much either), so how can you still afford to make great software? I feel shame if I can't make good software, and I don't want to make software so badly that I'll make bad software, but nobody pays well enough to make good software, and the market is so messed up it's almost impossible to sell commercial software that isn't bundled up as a solution of some kind. I can get around this some by selling SAAS on prem., but there's a limited utility in this: I could never build a new Smalltalk this way. Rust and Go have seemingly massive benefactors, but paying meagre salaries to their swarms of developers and activists: Nobody is getting rich but the vassals who were already rich to begin with. I've got a great idea for a new kind of programming language, but I don't have even a few million I can spend building it. It makes me sad that I can get paid so much more to not make software than I can get paid to make software.
- matfil 8y agoTwenty years ago (crikey, that long?), I was a pretty vocal Open Source advocate. At the time, it seemed like the only way to avoid a Microsoft monoculture, and I'm still not sure that wasn't true. But now we're seeing monocultures of corporate-sponsored open source (Chrome/Blink's dominance seems particularly alarming in this sense), and managers who are more reluctant than ever to accept technical solutions which aren't "standard". I'd love to know how to bring back a bit more diversity to everyday computing. Beyond using niche systems for hobby projects, leverage seems rather limited right now.
- 8y ago
- CrankyCanuck 8y agoGood old DT. Dave was a prof of mine in the late 1980's.. CompSci at Carleton in Ottawa, Canada. SmallTalk...my first reaction (95.202 for those that remember...) was WTF?? We had just done Pascal...SmallTalk just blew our minds. It was like you had to smoke dope first... you know, to get it. Many late nights in the lab... it was running in Mac emulation on ancient Lisa computers (I shit you not). Anyhow, none of really understood why we had to learn SmallTalk. There were certainly no summer jobs for SmallTalk guys (dBase? C? sure... ) But DT and the rest of the profs on the 5th floor extolled the value of Objects. Smalltalk is just the tool they said...to learn about OOP. DT always had the best lectures...he was a total blast to listen to. I may have even learned a few things. The only guys I knew that made a buck off of SmallTalk went to work for Dave at OTI. And then that got bought by IBM. Dave absolutely did well...I'm sure he's still smiling.