Death by a thousand frameworks. (TFW you’re about to start on a new JavaScript project.)
-
-
Replying to @aral
Advice as a professional JS developer: don't use any 'frameworks'. Use individual libraries, add them piecemeal, and only if you already have a problem that you know they can solve well. Devs way too easily fall into the trap of adding the entire kitchensink from some blog post.
1 reply 1 retweet 3 likes -
Replying to @joepie91
Always a balance, isn’t it? To find the right amount of abstraction so you don’t spend all your time reinventing the wheel & yet not over-optimising or adding too many layers of magic to it. I feel
@feathersjs &@vuejs get it right. But yes, every abstraction must earn its place.2 replies 2 retweets 7 likes
(My criteria usually is “does this framework/abstraction” enhance intent or obscure it? I rarely pick any library/framework that obscures intent – usually that’s a sign of premature optimisation – or doesn’t have a huge positive benefit to offset the additional cognitive load.)
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.