5 ms·
I'm not convinced that's "startlingly different in Haskell compared to the LISPs."
by dllthomas 13y ago
I'm not convinced that's "startlingly different in Haskell compared to the LISPs."
- taeric 13y agoMeaning you feel it is not that much more productive? Are there things in haskel that would make you recommend it over lisps?
- pdpi 13y agoFrankly, I'm starting to feel very strongly that static typing in and of itself makes you much more productive -- in the long run. Not so much because you write stuff faster, but because you spend less time patching it up.
- taeric 13y agoFunny, because I am coming to the other conclusion. Static programming is great when you can build one giant unified model of everything in your code. When you just want some parts that can be fitted together to get you what you want, dynamic programming is tough to beat. Consider, how many extensible editors (or other applications) have been written in Haskel? Or, really, any static language. Contrast that with how far emacs has managed to come. And, among the lisps, elisp is not highly regarded. For that matter, consider how far javascript has managed to take web programming.
- nbouscal 13y agoBoth of those examples obviously have very little to do with the quality of the language used, and everything to do with the ecosystems that were built around them.
- taeric 13y agoThen give me a compelling example otherwise. Also... I was not meaning to make an argument to the quality of the languages. If anything, my argument is admittedly about the ecosystems garnered by the different types of languages.
- mightybyte 13y agoYou're not going to get concrete comparable examples because Haskell has not had enough adoption and resources thrown at it to be able to compare it in this way. What I can do is point you at another comment I wrote about this the other day and the responses it got. https://news.ycombinator.com/item?id=7299034 https://news.ycombinator.com/item?id=7299034
- taeric 13y agoAmusingly, I was in that thread, too. :)
- nbouscal 13y agoThe problem with these massive ecosystems of dynamic code extensions is that when you layer leaky abstraction on top of leaky abstraction, each layer being broken in its own subtle ways, the end result is a ticking time bomb waiting to cost its users thousands or millions of dollars in lost productivity. Your example of JavaScript in web browsers is a perfect demonstration of this. We are the only engineering discipline where there are a significant number of people who actually think extensibility is more important than stability or robustness. Imagine a civil engineer pooh-poohing the stability of the bridge he's building, pointing instead to how easy it is to add additional lanes. Imagine a mechanical engineer decrying running a formal analysis of a new design for a car, saying "forget about that, look at how easily customers can plug in custom dashboard attachments!" This is lunacy, plain and simple.
- taeric 13y agoThis reeks of what I have seen as a common attitude among software developers where we make sweeping statements about other professions with little to back it up. I will not claim that extensibility is the be all end all attribute. I will claim that it is a valuable attribute. More so for some applications than others. Similarly, I will make the same claim for formal checked programs. In some fields/industries, why wouldn't this be the norm? So, if the claim is that static typing can make for a more completely specified application and that we should demand that for some fields. I agree. If the claim is that static programming is superior to dynamic, I take issue.
- tel 13y agoPersonally I feel like the gap between Haskell and Lisp is measured less in productivity (the way the gap between X and Lisp is for most Xs) but instead in comprehension and robustness. The code I write in Haskell might be only marginally easier to write than the similar lisp code, but it comes with much nicer, more sustainable structure and 60% of my unit tests for free.
- dllthomas 13y agoI've not done extensive development in any lisp, so I'm not able to make a robust comparison. There are clearly ways in which Haskell leads to more productivity (static typing when sufficiently expressive is a tremendous win), and some ways in which LISP has an advantage. It sounds plausible to me that it's a wash; something other than a wash is marginally more likely, but I'm not confident about which direction it would go.
- taeric 13y agoMakes sense. I think that mirrors my view, mostly. I have lately begun to fall on the side of lisp more so than haskel. Sadly, I can not really give a good reasoning as to why. I can say that finally going through SICP has been borderline mind blowing. It is hilarious/sad/crazy to see how many hot topics today were covered in a bloody introduction textbook from the 90s.
- dllthomas 13y agoOn a side note, this may be worth looking at: https://www.cs.drexel.edu/~mainland/2013/05/31/type-safe-runtime-code-generation-with-typed-template-haskell/ https://www.cs.drexel.edu/~mainland/2013/05/31/type-safe-run...