So, one age that tended towards a multiplicity of approaches for build and dependencies, and another with cheap networking that tended towards one agreed-upon solution. Haskell never had a blessed build and dependency distribution solution. It was my greatest roadblock, at least.

So anyway, my take is that Haskell landed between two software epochs: the C et al ecosystem, which had no central authority, two entirely different methods of distributing reused code, and many build systems; and then the web ecosystem, with tools built for that age, which tended toward singular.

Sorry for late reply, but I alluding to the Stack "vs" Cabal issue, and other more subtle issues that I don't fully understand, like why Linux distros like Arch have such a mess with libraries.

I'm far from the first, or most illustrious, voice sad about this. Have I mentioned Shake? lol

I want to also point out that calling any platform that Rust doesn't target "retro" to be over the line...

...for zero-cost and low-cost functional abstractions without needing a runtime.)

There is a wider issue with the preference for MIT/Apache dual licensing, over GPL3, imo. But the infrastructure dependence is a single point of failure, requires compromise of community values, and prevents organized action like bds.

I'm very new to the community (I was around for the lang's inception, but have been away since), and this dependence is striking, esp. given its reputation for consciousness.

In the wider FLOSS world, better alternatives have been used for a decade. Freedesktop on Gitlab is one example.