Re:Lamdu - towards the next generation IDE
by tel on Wednesday December 25, 2013 @08:55PM
(#6964989)
I find dynamic languages break my flow badly by eventually losing clarity on what things are supposed to do. Haskell is annoying as he'll to begin with but eventually those constraints give very tight, very fast feedback that's very flow-compatible.
Re:Lamdu - towards the next generation IDE
by Edmond on Wednesday December 25, 2013 @09:25PM
(#6965038)
Were you at the social innovation lab kickoff at Hopkins a few weeks back? I thought I saw a booth for Reify Health.
I wasn't personally, but I another guy on the team made it. Let me know if you'd like to say hi and grab a beer!
Re:Lamdu - towards the next generation IDE
by Edmond on Thursday December 26, 2013 @10:57AM
(#6966604)
sure, will be in touch!
Re:Lamdu - towards the next generation IDE
by freyrs3 on Wednesday December 25, 2013 @09:11PM
(#6965013)
Constraints are what prevent fallacious reasoning. It's better to have a tool/framework tell you you're wrong then not knowing about problems or believing falsehoods.
Re:Lamdu - towards the next generation IDE
by seanmcdirmid on Wednesday December 25, 2013 @09:26PM
(#6965040)
Again, there is tension between flow and feedback. The ability to express and tolerate incomplete and incorrect solutions when trying to solve, and more importantly, understand a problem, is very important. Bondage and discipline languages typically lack that capability, which is why many programmers are still flocking to dynamic languages. For this reason, even Haskell is trying to get into the hybrid typing game (type inference also helps of course, without which Haskell would be unusable).
Ideally, we could achieve flow without sacrificing semantic feedback (or vice versa). It is definitely a worthy goal
I've been fiddling with a System F language for a bit and find the types not as burdensome as I had originally thought. I couldn't imagine learning to use it from scratch though. I do think the loss of magic inference is a boon though.
http://en.wikipedia.org/wiki/Flow_(psychology)
The reason straight jackets lead to poor usability is that human minds are fairly diverse in the way they solve problems, and rigid constraints imposed by a tool are likely to trip up your thinking.
There is a tension between flow and feedback, but its not clear at all that one dominates the other as you've stated.