I tried writing some JavaScript today. I tried not to add any frivolous dependencies. I ended up with 18k dependencies. This is not a joke.
Show this thread
-
This Tweet is unavailable.
-
This Tweet is unavailable.
-
This Tweet is unavailable.
-
This Tweet is unavailable.
-
This Tweet is unavailable.
-
I mean I could see that argument, but that's not where we are now. In the time when I was writing a lot more JS most of what you saw were things like moment.js and underscore, which are reasonable sizes for that sort of library
From a technical point of view we should have seen the opposite trend. Back then you were shipping all the functions you never called unless you used the closure compiler which required additional changes to the code. Today with tree shaking it's no problem to have big libs
-
-
This Tweet is unavailable.
-
My take on this is that, since writing JS has been error prone for a long time (still is), a "unix" philosophy of doing only one thing well helped with reducing complexity of single packages. Less complexity leads to less room for error.
- 1 more reply
-
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.