> I think he forgets to mention Haskell, which is probably the reason > behind the shift of Swift towards optional values (Option type in > Scala, Maybe type in Haskell). You can't talk about modern type system > without talking about Haskell, Monads and Algebraic Data Types (Maybe > is a monad). > > I don't believe the future is dynamic typing, I believe it is type > inference and optional typing. There is no need to be radical about > it. One great sadly forgotten example of this is Strongtalk, which was > rumored to be the fastest implementation of Smalltalk ever made (I > don't know how it compares to the latest Pharo VM, though) and > included an optional strong type system I talked to some folks about Strongtalk at StS a few years back, and they told me that in order to achieve the speed improvements, they had to throw away type information. Basically, they tried to prove that static typing was faster, and proved the opposite.
I'd like to have that confirmed; it would challenge "conventional wisdom" on static typing. -Steven > (http://www.strongtalk.org/). Strongtalk team was bought by Sun before > they could release the language and their advancements in virtual > machine development were taken by the Java Virtual Machine. It is one > of my dreams to see Strongtalk back into action or maybe a version of > Self with optional typing, but I unfortunately lack the required > skills and time to do so. > > 2017-05-09 10:26 GMT-03:00 Ben Coman <b...@openinworld.com > <mailto:b...@openinworld.com>>: > > Fantastic article. Very well rounded. I particularly liked > "Meanwhile the Smalltalk programmers were scratching their heads > wondering what the big deal was. You see, their language was also > strongly typed; but their types were undeclared. In Smalltalk > types were enforced at runtime." > > and..."You see, the Smalltalk programmers had solved the missile > problem in their own unique way. They invented a discipline. Today > we call that discipline: Test Driven Development. ... You see, > when a Java programmer gets used to TDD, they start asking > themselves a very important question: “Why am I wasting time > satisfying the type constraints of Java when my unit tests are > already checking everything?” > > cheers -ben > > On Tue, May 9, 2017 at 2:49 PM, askoh <as...@askoh.com > <mailto:as...@askoh.com>> wrote: > > This is a quote from Bob Martin of "Clean Code" fame. Enjoy, > Aik-Siong Koh > > http://blog.cleancoder.com/uncle-bob/2016/05/01/TypeWars.html > <http://blog.cleancoder.com/uncle-bob/2016/05/01/TypeWars.html> > > > > -- > View this message in context: > > http://forum.world.st/Smalltalkers-will-eventually-win-So-says-this-old-C-programmer-tp4945895.html > > <http://forum.world.st/Smalltalkers-will-eventually-win-So-says-this-old-C-programmer-tp4945895.html> > Sent from the Pharo Smalltalk Users mailing list archive at > Nabble.com. > > >
