@brianleroux iow if my lib asks for "latest 1.x of time" and your lib asks for "latest 1.x of time", an app that includes both gets one copy
@brianleroux (return includes calling a callback from another module with an instance of a class from yet another module)
-
-
@wycats I feel like we should start talking about monads now -
@wycats its a joke. -
@brianleroux "you're saying complicated words so I don't have to listen to you, something something over engineering?" -
@wycats complicated
-
@brianleroux apologies for getting aggro right there. Probably misread you.
End of conversation
New conversation -
-
-
@wycats@brianleroux I think I get you. You skirt some of this if common classes are built-in/standardized. e.g. python datetime? -
@polotek@brianleroux but that restriction means shared types bottleneck on standardization (the opposite of the point of npm) -
@wycats@brianleroux it feels like this might be a bad idea w/ custom types. You'd be coupling modules together. Or maybe that's your point. -
@polotek@brianleroux it's common with things like http libs (shared request types) but people go into contortions to explain "bad idea" -
@wycats@brianleroux anyway, I'm not sure I'm adding much to the original convo. Just making sure I understood the core issue. -
@polotek@brianleroux JS hides the issue enough so people can say "antipattern" but it's more fundamental than thay -
- 1 more reply
New conversation -
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.