What kind of problems do you have with stack? I have never once had a problem with stack that wasn't solved by running stack upgrade. Stack is how I got started as a beginner; before that the only code I managed to run used the prelude. I am legitimately puzzled.https://twitter.com/dibblego/status/973710741860630528 …
-
-
Replying to @NathanLander
In short, stack over-specialises for the unlikely case, for a claimed benefit that doesn't actually exist. I am sympathetic toward beginners trying to get started, but stack is definitely not helping, even though those same beginners will claim otherwise. Progress is stunted.
2 replies 0 retweets 1 like -
Replying to @dibblego
I don't really understand how the stack use-case is that specialized. As I understand it, the assumption stack makes is that most developers don't need to worry too much about which version of some library they are using. That seems like most beginners and production teams.
1 reply 0 retweets 0 likes -
Replying to @NathanLander
"Most developers don't need to worry" about such and such. I have never worried about this thing, not for at least a decade before stack existed and not subsequently either.
1 reply 0 retweets 0 likes -
Replying to @dibblego
What tools do you use to avoid specifying every version number of your dependencies?
2 replies 0 retweets 0 likes -
Replying to @NathanLander
FWIW, version numbers are another example of stringly-typed programming nonsense. This horrible idea pervades not just stack and cabal, but almost our entire software industry. Imagine a world without version numbers. What is lost?
2 replies 0 retweets 0 likes -
Replying to @dibblego
If version numbers are too stringy, would you favor some kind of type for describing the usability/ build status and possibly another type for describing required dependencies?
1 reply 0 retweets 0 likes
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.