Smaller scale, this _has_ happened to Ruby. The first big disaster could have been rubygems. npm was just unlucky.https://twitter.com/iamdevloper/status/712743526086414336 …
-
-
Replying to @sarahmei
@sarahmei I don't think I agree with this. The fine details matter, and handling the `json` gem differently could have resulted in this.2 replies 0 retweets 1 like -
Replying to @sarahmei
@sarahmei I mean that the Ruby ecosystem has been more thoughtful about the *effects* of having a lot of dependencies.1 reply 1 retweet 1 like -
Replying to @wycats
@sarahmei when working on Rails 3, I wanted more deps (merger rationale!). DHH said no way: rubygems isn't good enough. We built bundler.1 reply 3 retweets 8 likes -
Replying to @wycats
@sarahmei there are costs and benefits to deps, but you can bend the curve if you respect the tradeoff.1 reply 1 retweet 1 like -
Replying to @sarahmei
@sarahmei I think so, yeah.1 reply 0 retweets 1 like -
Replying to @wycats
@wycats cargo vs bundler vs npm would make a fascinating talk/blog/book maybe#justsayin2 replies 4 retweets 22 likes -
Replying to @sarahmei
@sarahmei but where?!3 replies 0 retweets 0 likes
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.