by vq on 9/9/18, 9:25 AM with 14 comments
by forkerenok on 9/9/18, 11:58 AM
And I wouldn't say it's anything specific to Haskell: I've seen a lot of times in other languages people trying to flesh entire libraries around a domain-specific primitive that go far beyond their current needs.
I'd say the Haskell community (its focus) is more "at fault" here, encouraging these kinds of exploratory rabbit-hole-diving. Though, to be fair, there are people there with get-shit-done mentality (github/bos and github/ocharles come to mind) and I see more of that kind coming in lately.
Pick the weakest structure that will satisfy your current needs and move on. (by ocharles, paraphrased)
by jt2190 on 9/9/18, 3:31 PM
It's fair to question the tool in this case. As programmers we rely on our tools to provide abstractions that free our minds from thinking about details that don't matter. If the tool (or perhaps the culture around using the tool) insists that we deal with details we're not interested in or don't care about, perhaps the tool is not the best one for the task at hand.