Here's why AMD was a shitty idea: https://medium.com/@trek/last-week-i-had-a-small-meltdown-on-twitter-about-npms-future-plans-around-front-end-packaging-b424dd8d367a …
-
-
Replying to @samfosteriam
@samfosteriam not about taste. There was an opportunity to standardize across client and server. It was lost because of AMD.@getify@trek2 replies 0 retweets 0 likes -
Replying to @tobie
@tobie@samfosteriam@getify you could also say it was lost because CJS wouldn’t conceded on sync/asnyc.2 replies 0 retweets 1 like -
Replying to @trek2 replies 0 retweets 0 likes
-
Replying to @samfosteriam
@samfosteriam except CJS supported both, just needed a build step for the (async) transport.@trek@getify3 replies 0 retweets 0 likes -
Replying to @tobie
@tobie AMD predates browserify@samfosteriam@trek@getify1 reply 0 retweets 0 likes -
Replying to @wycats
@wycats there were plenty of CJS-based solutions written before AMD.@samfosteriam@trek@getify1 reply 0 retweets 0 likes -
Replying to @tobie
@tobie none of them were very successful@samfosteriam@trek@getify1 reply 0 retweets 0 likes -
Replying to @wycats
@wycats true. None had a fancy website. Which was silly in retrospect.@samfosteriam@trek@getify1 reply 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.