This has become everyone's go to lazy reasoning for not sufficiently abstracting complexity into understandable components.
right, which is sorta what people who are doing it right mean by "scale"
-
-
we need a better term because "scale" has too much architecture astronaut glued onto it.
-
I think nobody would disagree that npm "scales" better than go get.
-
i do think we need a better word but it's hard to beat a word that means so many different things people identify with.
-
"scale" is abused and "framework" is now a term of derision ;)
-
ecosystem scale is not something people carefully consider. (you wrote some good stuff on this back in the day that got me thinking)
End of conversation
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.
