@glenathan @sdboyer so not much time to nail even the entire spectrum of known solutions, just the most important.
-
-
Replying to @wycats
@wycats@glenathan well, i'm no rustacean yet, but it seems you did a pretty bangup job1 reply 0 retweets 0 likes -
Replying to @sdboyer
@wycats@glenathan which, IMO, is an argument for "big picture" doc's value (be it my article or not) - codesign PM w/lang is goooood1 reply 0 retweets 0 likes -
Replying to @sdboyer
@sdboyer@glenathan I think SAT solvers are a part of the solution, but they miss constraint weighting (when is a "conflict" a conflict?)3 replies 0 retweets 1 like -
Replying to @wycats
@sdboyer@glenathan On the other hand, constraint solvers are heavyweight and can hide the tradeoffs in scores and math.1 reply 0 retweets 0 likes -
Replying to @wycats
@sdboyer@glenathan This is the last mile for me personally. The thing I am trying to solve right now for Cargo.1 reply 0 retweets 0 likes -
Replying to @wycats2 replies 0 retweets 0 likes
-
Replying to @glenathan
@glenathan@sdboyer this is fundamentally the problem with npm's solution: it assumes dependencies can usually be considered internal.2 replies 0 retweets 0 likes -
Replying to @glenathan
@glenathan peerDependencies are considered, by the npm ecosystem, to be an antipattern. More deps are shared than they think.2 replies 0 retweets 0 likes
@glenathan and making humans resolve dependencies of any kind is not a recipe for a composable ecosystem.
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.