Death by a thousand frameworks. (TFW you’re about to start on a new JavaScript project.)
-
-
(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.)
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Well, yes and no. The balancing act mostly applies to monolithic frameworks - with modular dependencies, it's much easier to swap in dependencies as you find yourself needing them during the project, without having to decide on them upfront.
-
I feel like that's where the kitchensink "all the frameworks" problem in JS *really* comes from - people used to monolithic ecosystems where you *have* to decide your dependencies upfront, and carrying over those habits to a modular ecosystem where that isn't necessary.
-
Indeed. We have npm for a reason :)
-
Yep. Unfortunately a lot of devs seem to find it hard to adapt to modular design, carry over monolithic habits, and then blame the modular ecosystem for not working well with their habits :/ (It doesn't help that there's little documentation on how to design modular code...)
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.