@glenathan @sdboyer I built the first usable version of cargo end to end with @carllerche end to end in 3 months and we "finished" in 6.
@glenathan peerDependencies are considered, by the npm ecosystem, to be an antipattern. More deps are shared than they think.
-
-
@wycats that was the idea when deprecation was floated. The ensuing discussion reached a different conclusion though -
@wycats peerDeps now act as a hint to generate warns, but don't auto-install peers. Recommended for plugin systems, React, gulp, grunt etc -
@glenathan that idea allowed them to avoid designing a real system: "you can resolve deps better than a computer" nope -
@wycats Perhaps so - but I'm not sure what else you can do if a dep has state. You have to have only 1, so if there's a version conflict..?
End of conversation
New conversation -
-
-
@glenathan and making humans resolve dependencies of any kind is not a recipe for a composable ecosystem.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.