Haskell

“Problem specifically in Haskell is that you have to worry about implementing tail recursion to get efficient stack usage.”

“I program Haskell all the time, and I encounter "non-bugs" where the compiler prevented me from doing something”

“I've read many more studies over the years and NEVER seen one showing a significant advantage for Haskell and similar languages.”

“Back when I was a beginner actually interested in getting out of the beginner step of Haskell, this was an issue for me”

“the language supports (enforces) good decision making; static typing w/ inference and a functional style as a first class concept”

“Haskell still strikes me as more “ergonomic,” better suited to express abstractions, and just closer to the ideal of a language that helps the developer think.”

“Haskell's type system is fully turing complete. Strictly speaking, it can encode anything any other program can.”

“Fast compile times is one of the most important qualities for developer productivity. It made Haskell a non-starter for many developers”

“the glorious (almost almighty) Haskell compiler is too slow for the agent to iterate it's mistakes until it gets it right”

“Haskell is a border case between sides because the idea of PL is so light that using so much light in programming leans to be really dark.”

“you would have to work hard to find a domain constraint that you can't declare in the Haskell type system”

“Haskell is I think a great language for llms - just make everything as pure as possible and you are golden.”

“Laziness by default and Hindley-Milner type inference seem like mistakes that simply aren't going to get cleaned up.”

“The thing that's so elegant about Haskell is that it allows you to express programmatic constructs at a very abstract level.”

“Having an entire ecosystem seemingly more concerned about writing theses about type theory than with building usable libraries?”

“The type system lets you very quickly figure out what something is before you figure out what something does”

“other languages that follow a stricter/larger compile time regimen e.g. Haskell, OCaml, Idris, ATS, F* would be suitable as well for this kind of approach”

“Haskell is incredible for medium-sized programs, but it has its own missing modularity features that make it non-ideal for large programs”

“ported an old service at a previous company to Haskell and tried to productionize it enough for our staging environments”

“they are still mindbogglingly complex when it comes to telling the programmer if the next line is the right amount of space”

“Haskell is top tier when it comes to syntactic and conceptual elegance. The biggest problem is tooling, I would say.”

“both positive (fusion, elegant expression of infinite structures) and negative (space leaks, reasoning difficulty about resource usage)”

“In Haskell it's just more economic and better integrated with the rest of the language and its typesystem.”

“the maybe most wide used functional language (Haskel) has a very bad reputation about being unnecessary complicated and obscure”

“having experience in large commercial Haskell projects, I can tell you the web apps also suffer from the dreaded dependency explosion”

“no mutability makes it reason to think about, fully statically typed, excellent compiler and diagnostics”

“Haskell strikes the perfect balance here, I've worked at companies with massive codebases where maintaining is still a breeze years later.”

“my experience writing parsers in Haskell and handling error cases succinctly through functors was such a pleasant departure”

“Haskell is great, but its entire vibe (lazy evaluation, pure functions) is entirely different from what Python's about.”

“The high level declarative nature and type driven development style of languages like Haskell also make it really easy for an experienced developer to review”

“strong type systems like what Haskell or to a lesser extent Rust have to offer are useful as safeguards for anyone”

“It's also super easy to find them and haskell-language-server can even suggest which functions you want based on signatures you have.”

“If you used that or Haskell for a while in a non trivial way it will give you deeper insight into why types matter”

“Purely functional code is easier to test because of its referential transparency and lack of shared state.”

“If the generated code uses a suitable programming language, like the safe subset of Haskell, then the risk is significantly lower.”

“a new user having to juggle immutability, IO and monads all at once at the same time will be almost certainly impossible.”

“STM shines in a concurrent setting, where you know you'll multiple threads accessing your system and you want to keep everything correct.”

“they do not in any way give you the same level of guarantees that OCaml, Haskell, or Rust would give you.”

“If you just want to explore a functional language from the ML family to get some familiarity, Haskell might be the better bet.”

“This makes the language feel a lot less experimental, as you don't generally have to enable 10s of extensions to get things working.”