Re: [Pharo-users] Smalltalkers will, eventually, win. So says this old C++ programmer.

> Hi kilon, > > Some weeks ago I tried the C live programming technique for the Ludum Dare. > It works very well. For that occasion I wrote this short article > https://ldjam.com/events/ludum-dare/38/smalcoded-a-small-eco-destroyed-world/a-diabolical-game-for-a-diabolical-experiment > . The game

Re: [Pharo-users] Smalltalkers will, eventually, win. So says this old C++ programmer.

This is revelation to me. I am enduring 10 minute turnaround for every edit > I make in *.java, xml, jsp, js files. 4 minute compile and 6 minute web > server update. How can I get that shortened to 10 seconds say? What links > can help? What search terms to google? > 10 minutes o_O wow, I can

Re: [Pharo-users] Smalltalkers will, eventually, win. So says this old C++ programmer.

Hi kilon, Some weeks ago I tried the C live programming technique for the Ludum Dare. It works very well. For that occasion I wrote this short article https://ldjam.com/events/ludum-dare/38/smalcoded-a-small-eco-destroyed-world/a-diabolical-game-for-a-diabolical-experiment . The game ended pretty

Re: [Pharo-users] Smalltalkers will, eventually, win. So says this old C++ programmer.

Or BeanShell http://www.beanshell.org/ or Groovy https://zeroturnaround.com/rebellabs/scripting-your-java-application-with-groovy/ or Spring-Shell https://projects.spring.io/spring-shell/ Example app I am using (and extending) for Hadoop work: https://github.com/sequenceiq/ambari-shell When

Re: [Pharo-users] Smalltalkers will, eventually, win. So says this old C++ programmer.

There is a Java REPL. You could Google that. There's also a some kind of commercial hot/live compiler tool called "JRebel". Haven't tried it (don't code Java). On Wed, May 10, 2017 at 4:29 AM, askoh wrote: > Kilon: > > This is revelation to me. I am enduring 10 minute

Re: [Pharo-users] Smalltalkers will, eventually, win. So says this old C++ programmer.

Kilion, In Haskell (a language that I love, just as Smalltalk) you have the REPL. The workflow is, while you are working on the project, you periodically load that file into the REPL and check. After that you compile. Haskell works with a strong type inference feature, however most Haskellers will

Re: [Pharo-users] Smalltalkers will, eventually, win. So says this old C++ programmer.

Kilon: This is revelation to me. I am enduring 10 minute turnaround for every edit I make in *.java, xml, jsp, js files. 4 minute compile and 6 minute web server update. How can I get that shortened to 10 seconds say? What links can help? What search terms to google? Thanks, Aik-Siong Koh >

Re: [Pharo-users] Smalltalkers will, eventually, win. So says this old C++ programmer.

Just to remind people here that all languages with long compile times can be avoided live coding style through the use of dynamically linked libraries known as DLLs on windows, shared libraries on linux (*.so) and macos (*.dylib) . Also Swift in particular comes with a live coding environment

Re: [Pharo-users] Smalltalkers will, eventually, win. So says this old C++ programmer.

On Tue, May 09, 2017 at 06:59:08PM +0200, Stephan Eggermont wrote: > I don't know. I do know that I can't use something with the > ridiculous compile times of Haskell or Swift. That just kills flow > and productivity. You could hop onto an office chair and engage your colleague in sword fighting.

Re: [Pharo-users] Smalltalkers will, eventually, win. So says this old C++ programmer.

Let me add that I am perfectly happy with the system given the type and size of applications I do write and maintain. And having flow is #1 criteria for enjoying my work. Phil On Tue, May 9, 2017 at 6:59 PM, Stephan Eggermont wrote: > On 09/05/17 16:17, Eric Velten de Melo

Re: [Pharo-users] Smalltalkers will, eventually, win. So says this old C++ programmer.

On 09/05/17 21:22, Steven R. Baker wrote: I'd like to have that confirmed; it would challenge "conventional wisdom" on static typing. I don't recall details but I have read that no static type information was actually used for "speeding up", it was all PICs etc. So yes, an interesting fact.

Re: [Pharo-users] Smalltalkers will, eventually, win. So says this old C++ programmer.

> 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).

Re: [Pharo-users] Smalltalkers will, eventually, win. So says this old C++ programmer.

This is why three years ago a convinced Pablo Tesone and Nicolas Passerini to work on a Type Inferencer for Pharo. Now the economic situation in argentina pushed Pablo to take another grant. And this is why we proposed as a topic to new guy in our team to work on this topic. Unfortunately the

Re: [Pharo-users] Smalltalkers will, eventually, win. So says this old C++ programmer.

On 09/05/17 16:17, Eric Velten de Melo wrote: 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

Re: [Pharo-users] Smalltalkers will, eventually, win. So says this old C++ programmer.

On Tue, May 9, 2017 at 10:02 AM askoh 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 > > > > -- > View this message in context: >

Re: [Pharo-users] Smalltalkers will, eventually, win. So says this old C++ programmer.

I agree with Eric that some future programming environments will probably provide and encourage optional types + type inference. This doesn't necessarily contrast with late dynamic binding à la Smalltalk. If types are an entangled part of the language, like in virtually any statically typed

Re: [Pharo-users] Smalltalkers will, eventually, win. So says this old C++ programmer.

2017-05-09 5:59 GMT-03:00 Sven Van Caekenberghe : > Great article. Thanks for sharing. > > Not that I or most people here need convincing, but it is nice to see others > voicing this opinion. +1 Not only the opinion, but it is good to see somebody with such influence recognizing

Re: [Pharo-users] Smalltalkers will, eventually, win. So says this old C++ programmer.

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

Re: [Pharo-users] Smalltalkers will, eventually, win. So says this old C++ programmer.

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

Re: [Pharo-users] Smalltalkers will, eventually, win. So says this old C++ programmer.

Great article. Thanks for sharing. Not that I or most people here need convincing, but it is nice to see others voicing this opinion. > On 9 May 2017, at 08:49, askoh wrote: > > This is a quote from Bob Martin of "Clean Code" fame. Enjoy, Aik-Siong Koh > >

[Pharo-users] Smalltalkers will, eventually, win. So says this old C++ programmer.

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 -- View this message in context: http://forum.world.st/Smalltalkers-will-eventually-win-So-says-this-old-C-programmer-tp4945895.html Sent from the Pharo