JavaScript: We must ensure backward compatibility at all cost Also JavaScript: All the libraries you used 2 years ago are abandoned
-
-
-
It does matter what specific combos of libs you picked 2 years ago. Did some kind soul build the the gulp-webpack-karma-jquery bridge for you to cross?
-
Absolutely. It also matters what libraries your current library maintainers picked two years ago... and what those library's maintainers picked two years before that.
-
For example, if you `npm install` in webpack from source, almost every vulnerable module that's introduced was published ~3 years ago – probably meaning that they're mostly dependencies of the same module
pic.twitter.com/Xw8bfMXxLf
End of conversation
New conversation -
-
-
That'll happen but not to anyone practicing so-called "vanilla" JavaScript. I feel the treadmill beating beside me but I'm not on it or subject to the whims of fashion.
-
I think on/off is not a great analogy. The spectrum is wide and multi-directional. no true vanilla javascript :)
-
bunch of plain esmodules streaming down in parallel to any evergreen browser feels as true as can be to me; likewise simple bare require statements in node-land. sure it'd be nice if they had the same system for modules but they don't and that isn't a big deal imo.
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.