a good test is whether the"at scale" argument comes along with "also makes it easy for beginners and bootstrapping"
-
-
Replying to @wycats
exactly. half the the time "at scale" means "when a week long on-boarding into our stack is common."
1 reply 0 retweets 2 likes -
Replying to @mikeal
yeah. "beginners through advanced users can all use this" needs some glue, but less than astronauts believe.
1 reply 0 retweets 0 likes -
but also, apps built with no-stack can end up with longer onboarding
1 reply 0 retweets 2 likes -
Replying to @wycats
on a long enough timeline "no stack" becomes "crazy custom stack we have glued together just for this app"
1 reply 0 retweets 3 likes -
Replying to @mikeal
right, which is sorta what people who are doing it right mean by "scale"
1 reply 0 retweets 0 likes -
we need a better term because "scale" has too much architecture astronaut glued onto it.
1 reply 1 retweet 0 likes -
I think nobody would disagree that npm "scales" better than go get.
1 reply 0 retweets 0 likes -
Replying to @wycats
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.
1 reply 0 retweets 0 likes -
Replying to @mikeal
"scale" is abused and "framework" is now a term of derision ;)
1 reply 2 retweets 4 likes
ecosystem scale is not something people carefully consider. (you wrote some good stuff on this back in the day that got me thinking)
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.