-
Honestly, after fighting this fight for a decade now and building a ton of websites, the default still strongly confuses me. The sites that actually need this complexity are outliers and they always have been. simonw/1499137212234956802Permalink On twitter.com
♻️ 1 Retweets ❤️ 11 Favorites 2022 Mar 2 Mood -3 🙁
-
…in reply to @jefflembeck
These frameworks are amazing technological feats, for certain. And the work that goes into them is _super_ neat and worth understanding, but the odds that you need them are low. Extremely low.On twitter.com
-
…in reply to @jefflembeck
Defaulting to them means defaulting to significantly more complexity. Frequently before you’ve figured out where your architecture issues even will be.Permalink On twitter.com
-
…in reply to @jefflembeck
My assumption when choosing them in the past was ALWAYS team-related. People wanted to know these things so they could go on to other companies that use it because they picked it for team reasons which they picked it because you can make $500k comp at some FAANG that uses itPermalink On twitter.com
-
…in reply to @jefflembeck
And that’s a hell of an incentive, but it’s making the web a worse place and it’s actively harming engineering teams one after another.Permalink On twitter.com