Haskell to me felt exactly like what you described: I could get stuff done fast because of how few head-scratchers I'd experience. This is mostly due to type mismatches, and how much more well thought our my design needed to be upfront. I also really enjoyed the language because I could express fairly complex thoughts in a very succinct, and yet very readable fashion, mostly thanks to types being explicit and enforced at compile time. Code reuse and sharing across multiple applications is also a breeze, which is absolutely key once you get past the "single Rails app" stage and you start getting into two digits worth of tools, services and applications.
* Statically safe metaprogramming.
* Well designed access rights (private, public).
I also really like the type system, very well designed.
Disclaimer: I do not have enough PL type theory under my belt to confidently make this argument.
I despise that people give their 2 cents for something they haven't experienced much.
>I have ... very little experience with Haskell
So, how would you know?
It seems rather hard to evaluate the tail end from "little experience".
Do you have experience using haskell? If not, you are being hypocritical. Please stop.
Yes, that's what banks are most known for. Showing off how clever they are and not doing anything useful. Facebook and google certainly fit that profile as well right?
Not always true, sometimes you can have a fairly good picture of something after a short time.
And I just don't find Haskell (or Lisp) to be as productive as many would suggest, even if you adjust for matureness of the ecosystem. (Note: I have a moderate experience with Lisp, very little experience with Haskell and these days mostly program in Java, Julia and Python.)