33 ms·
> the tooling is decades behind, say, Rust or Go That's definitely not true, even if that was true maybe 6 years ago. As someone who's uses Haskell daily and
by jose_zap 4mo ago
> the tooling is decades behind, say, Rust or Go
That's definitely not true, even if that was true maybe 6 years ago. As someone who's uses Haskell daily and also many other languages, I can see Haskell's tooling as more advanced than many others.
- mirpa 4mo agoThink problem is not in advanced features but in stability, integration and streamlining - compared to Rust/cargo.
- the-grump 4mo agoThis is exactly what I meant. It's not the ability to build things; of course you can. The progress has been in agreeing on a coherent interface everyone uses and which handles 99% of what most projects need with minimal friction.
- drewfax 4mo agoI tried building a cross platform shared library. I still couldn't get GHC to generate the library with Haskell's Runtime (RTS) statically linked. Tried multiple AI models and nothing could make it work. Eventually gave up after a month. Also there's no support for Android and iOS, atleast not without spending months in recompiling GHC with haskell.nix or other third party projects. Eventually I switched to Rust. It's tooling is so mature that I can focus on developing than compiling GHC. Despite these demerits, I love Haskell language and lazy eval. I wish I can use it one day.
- mietek 4mo agoI built an example project showing how to build shared libraries in Haskell, in 2019. https://github.com/mietek/haskell-so-example https://github.com/mietek/haskell-so-example