I have this data *in spades*. Not looking good for the folks who blindly hire for framework skills.
-
-
Replying to @slightlylate
Any chance any of that data might be opened in the future? That would, like, really help. Not that you didn't know that already.
2 replies 0 retweets 2 likes -
Replying to @ppk
Generally I see it in consultation with sites pre-launch or early in their process; don't want to shame teams.
3 replies 0 retweets 1 like -
Replying to @slightlylate @ppk
Contra
@stubbornella, I don't see framework use link with "top talent"; it's nuanced.1 reply 0 retweets 0 likes -
Specifically, I see a strongly bi-modal distribution. A tiny fraction are amazing and would thrive w/ any toolchain...
1 reply 0 retweets 1 like -
...those teams adopt FWs but also take them apart and put them back together in leaner, meaner configurations.
1 reply 0 retweets 2 likes -
Those teams also tend to have a bias toward less-opinionated stacks (because rebuilding/reconfiguration).
1 reply 0 retweets 0 likes -
For the other side of the distribution, those choices are *toxic*. And that's basically everyone.
1 reply 0 retweets 2 likes -
Most folks aren't using frameworks as an accelerant to what they know they wanted, they're using them as a level-up. Access to a higher tier
1 reply 0 retweets 2 likes -
...but they don't know what they don't know, so when the community leaves things as an exercise to the reader, it's pure perf/UX
#fail1 reply 0 retweets 2 likes
*this is nearly every app I trace* Opinionated stacks are better for nearly all, but not "cool".
-
-
For ~every team in '17, starting with a framework and not an opinionated starter-kit that gets build, code-splitting, etc. right is

2 replies 0 retweets 3 likes - 6 more replies
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.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.