@wycats My point is that it doesn't add any burden on framework authors, only on code that calls them. It's generic, not ad-hoc.
-
-
Replying to @robotlolita
@robotlolita it requires all framework modules to create another level in each module so they become generative and parameterized.1 reply 0 retweets 0 likes -
Replying to @robotlolita
@robotlolita@wycats This thread reads to me as 'npm precludes modules from assuming implicit global state', which seems fine to me.3 replies 1 retweet 7 likes -
Replying to @mountain_ghosts
@jcoglan@robotlolita It seems fine to you, and that is an explicit technical decision.1 reply 0 retweets 0 likes -
Replying to @wycats
@wycats@robotlolita What I mean is that npm's design has, with hindsight, improved the design of my programs.2 replies 1 retweet 6 likes -
Replying to @mountain_ghosts
@wycats@robotlolita I don't see the lack of global state as a limitation, like I did in the early days.5 replies 0 retweets 1 like -
Replying to @mountain_ghosts
@jcoglan@robotlolita In current npm, if I have two packages that depend on ember-metal, I get two copies.3 replies 0 retweets 1 like -
Replying to @wycats
@wycats@jcoglan@robotlolita and they can be different versions! its the first system to *not* have dependency hell ffs! thats a huge win!4 replies 1 retweet 1 like -
Replying to @brianleroux
@brianleroux@wycats@jcoglan@robotlolita if 50 packages require the same library you get 50 copies all of which can be different versions?4 replies 1 retweet 2 likes
@bascule @brianleroux @jcoglan @robotlolita But a(b()) where b() returns C1 and a() takes C2 equals explosion.
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.