On Mon, Mar 28, 2011 at 8:39 PM, Brandon S Allbery KF8NH <[email protected]> wrote: > Somehow the Haskell community is hellbent on repeating the mistakes every > other community learned about the hard way years ago, especially in the area > of dependencies (first refusing to acknowledge the need for upper dependency > limits, more recently trying to avoid adding an epoch — and I'm not counting > how packages included with the compiler but not recognized as such by Cabal > lead directly to Cabal introducing diamond dependency failures). Is this > *really* necessary, or should those of us who've seen it before just sit > back and watch you all ram your heads against the same brick walls? > > (Why no, it doesn't look like a brick wall now; that's the point. It > *will*. Learn *before* it happens.)
Hi Brandon: are any of these lessons written up somewhere? (I'd love to be able to read about what the important ones are, their rationale, etc.) Thanks, Robby _______________________________________________ Haskell mailing list [email protected] http://www.haskell.org/mailman/listinfo/haskell
