I came across Haskell in 2013 and was hooked. For better or worse, I am a Windows user. mentions me above, so I thought I would explain my interest in Stack. Hello! I came across this ‘discourse’ tonight, via Stack Governance. I’m not happy with the current situation which is that Stack is “feature complete” and blocking innovation (Backpack) and is not integrating well with other tools (HLS & GHCup). But in the past few months, as I’ve been thinking about where I wanted to spend my limited time after the babies were born, I decided that it was time to call out Stack as needing motivated maintainers, or to see it sit in a feature complete, non-evolving state. I’ll continue maintaining the project in its current state, together with other maintainers currently doing so. If people want to see changes and improvements to Stack, you need to get involved personally. In other words, this is a more serious call to action than I’ve made previously. And I know regressions in Stack with newer GHC/Cabal versions (like overly aggressive recompilation, or broken deregister support for private libraries) causes the Stackage team pain and suffering. I know that it becomes a blocker for the Stackage team sometimes. I’m not sure how large an overlap there is between Stack users and people looking to use the latest GHC and Cabal features that it doesn’t support. People are free to take those statements as they will. That never came into existence, and so now I feel pretty comfortable in saying: outside of making sure Stack continues to work for my primary use cases, I’m not going to be investing my own time much going forward. I had hoped that with the Haskell Foundation launch this year, we would have an affiliation process for projects that allowed better interproject communication and reduced the maintenance burden. I haven’t said this before, but I’ll say it now: I’m not interested in investing any time in staying on that treadmill, or introducing new features to Stack. Most of my pain points come from changes coming upstream from GHC or Cabal causing breakage, or introducing new features (like multiple libraries per package) that require large overhauls to how Stack operates. Frankly, for all of my needs, it’s checking the boxes right now. I don’t maintain it alone, but none of the maintainers are spending a significant amount of time on it. Stack is by far the largest project I maintain. Especially the part about stack: Special call out: Stack And of course stackage will probably still stay relevant, but I want to focus on the command line tool for this discourse topic. Although I wasn’t really around yet, I’ve heard that it was quite a big improvement at the time and it seems to have made Haskell more attractive for industry. That might be a good thing, but I would at least hope to see some official announcement about the direction of the project.Īnd of course I don’t want to downplay the achievements of the developers of Stack. I have once recommended stack to newcomers because it seemed like a more streamlined experience, but now I fear that it is slowly fading out as the competition (cabal and ghcup) are incorporating all of its features. Looking at their contributor activity on GitHub shows that the volume of commits and changes is fading since about 2019-2020. They don’t have support for backpack and cannot install HLS, and they don’t seem to want to add support for GHCup. Is (the command line tool) stack still actively developed? I’ve heard about bugs that have been known for years. Continuing the discussion from GHCUp button on I haven’t seen much presence of official stack communication online in recent years.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |