4 ms·
My point can be generalized, sure. But you haven't substantiated the idea that most people who try both Java and Haskell/Lisp will prefer Haskell/Lisp. That's p
by throwawaymath 8y ago
My point can be generalized, sure. But you haven't substantiated the idea that most people who try both Java and Haskell/Lisp will prefer Haskell/Lisp. That's precisely why my very general point is applicable - your claim is sufficiently unsupported that I can simply reverse the hypothesis and we have no more or less information than we started with.
If you'd like, I can trade anecdotes instead - I used to work at a company with a large codebase consisting of nontrivial Java, Clojure, Scala and Haskell. Nearly every engineer I spoke to preferred Java (and I had to interact with nearly all the 300 engineers who worked on it).
Now at this point it may seem like I'm being a curmudgeon. But the reason I'm harping on this is because your implicit claim is that Haskell/Lisp are better languages for either productive or aesthetic reasons. But I don't think that's a fair statement - they're different languages, suited to different tasks. You shouldn't draw the conclusion that people who have e.g. moved on to Haskell from Java are representative of most Java developers. It's equally plausible that most Java programmers don't want to move on from Java, and so wouldn't like Haskell if they've tried it. Or perhaps they have tried it and simply didn't jive with it.
- willtim 8y ago> they're different languages, suited to different tasks. What tasks exactly do you think Java is better suited to than Haskell? The "innovation" of Java was to take the runtime of a high-level language and combine it with the productivity of a low-level one. It is not well particularly suited to systems programming or high-level programming (e.g. ML and analytics, parallelism, concurrency).