5 ms·
> 4. Though in fairness, I am just goofing around with Smalltalk and if I had production grade concerns, I might have a different attitude. I'm curious, is Sma
by kwhitefoot 10y ago
> 4. Though in fairness, I am just goofing around with Smalltalk and if I had production grade concerns, I might have a different attitude.
I'm curious, is Smalltalk especially good for any particular task? Or especially easy to use for something?
I'm always on the look out for something better as all the languages I use and know well seem inadequate or tedious in one way or another and a lot of those that I don't use seem intimidatingly difficult to get started with (often because ecosystem in which they live is difficult to handle).
- brudgers 10y agoSmalltalk 80: the langauage is formally divided into three parts. The third part is devoted to simulations such as a car rental agency (one of the examples). I was a bit surprised, but then I remembered that Smalltalk's object oriented predecessor was Simula (as in 'simulation'). The code for the simulation examples is compact because Smalltalk includes 'primitives' that are suited for building simulations. From a more mundane language design standpoint, Go's capital/lower syntax for 'public' versus 'private' identifiers in modules mirrors Smalltalk's public/private syntax for object methods/variables.
- gaius 10y agoI'm curious, is Smalltalk especially good for any particular task? Or especially easy to use for something? Have a read of http://www.cincomsmalltalk.com/main/successes/financial-services/jpmorgan/ http://www.cincomsmalltalk.com/main/successes/financial-serv... But then consider that they didn't choose Smalltalk for the next project...
- throwaway7645 10y agoWhat did JPMorgan use for their next project?
- gaius 10y agohttp://techcareers.jpmorgan.com/cm/BlobServer/athena_jpmc.pdf?blobkey=id&blobwhere=1320615212303&blobheader=application/pdf&blobcol=urldata&blobtable=MungoBlobs http://techcareers.jpmorgan.com/cm/BlobServer/athena_jpmc.pd... C++ and Python
- throwaway7645 10y agoYea, I often wonder about this kind of thing. Compared to Fortran, Common Lisp is a tower of power and sorcery, but compared to Python it isn't as impressive. Yes, it is a more powerful language, but the power isn't always worth the learning curve and mostly abandoned libraries. I think Python + C++ seems to be an easy spot marrying rapid prototyping & raw speed when you need it in addition to all the developers you'd get from 2 of the top 5 languages in amount of use. The Smalltalk and Common Lisp ecosystems are pretty similar to me. Both have a few commercial products and a few open source projects and a fairly small and fragmented community despite some commercial success.
- brudgers 10y agoA lot of Common Lisp libraries are done rather than abandoned [Clojure inherits this property]. Common Lisp is stable because the spec is about twenty-five years old. Hence new behaviors introduced by software updates are either implementation extensions or regressions. If a new version of a Common Lisp implementation breaks an existing library, it is more likely a regression than a library corner case...and because libraries are stable, it is practical to test against what people are using in the field. I think Python and C++ are great languages, but when comparing them to Common Lisp -- or Smalltalk or discussing their merits in general -- there is the question of which Python and which C++ form the basis of comparison.
- gaius 10y agoThat is true in the sense that the fundamental algorithms and data structures and so on are maths and maths doesn't change. But the vast majority of them are available in Python libraries, and if you need something right now say a library interfacing to a particular DB or protocol, there is a very high probability that in Python you can pip it in a minute and it will basically work, vs having to do it yourself in Lisp - and it's not cool fun stuff like a new algorithm, it's dull boring work of reverse engineering and hacking around the bugs in someone else's product, and Lisp doesn't give you any leverage there.
- hota_mazi 10y agoIt's worth spending a few hours to get an idea of what Smalltalk looks and feels like, but I wouldn't spend any more time than that on it. First of all, it's dynamically typed, which is not something we should seriously be using in the 21st century. Second, the tool ecosystem surrounding Smalltalk is abysmal and antiquated compared to modern IDE's.
- coldtea 10y ago>First of all, it's dynamically typed, which is not something we should seriously be using in the 21st century. Citation needed. >Second, the tool ecosystem surrounding Smalltalk is abysmal and antiquated compared to modern IDE's. Actually modern IDE's are abysmal compared to what Smalltalk offered even back in 1995.
- hota_mazi 10y ago> Citation needed Math. Look up the Curry Howard isomorphism and why it cannot be leveraged with dynamically typed languages. > Actually modern IDE's are abysmal compared to what Smalltalk offered even back in 1995 I think you should spend some time with some of these modern IDE's to understand what true, guaranteed correct refactoring means, something Smalltalk can never hope to achieve because the language doesn't have type annotations.