4 ms·
So, basically, you end up rewriting the glue code and plumbing, keeping track of twenty-eight security bulletins instead of one, and hoping that someone doesn't
by ebiester 12y ago
So, basically, you end up rewriting the glue code and plumbing, keeping track of twenty-eight security bulletins instead of one, and hoping that someone doesn't get a zero-day in a less used library that doesn't has much security attention paid to it.
And that's fine, if writing a framework per project is something you have time for. But make no mistake -- you're writing a framework.
- williamcotton 12y agoyou end up rewriting the glue code and plumbing I'm not sure what you mean. Can you give an example? keeping track of twenty-eight security bulletins instead of one, and hoping that someone doesn't get a zero-day in a less used library that doesn't has much security attention paid to it System administrators, developers of pretty much any language, and even chip designers have to deal with the issues related to code that wasn't written in-house. We live in a modular world. But make no mistake -- you're writing a framework. React and the Common JS module system are enough of a framework especially when compared to jQuery. I'm getting the feeling that most people on this forum don't really know nor care how these tools work and are mainly interested in making snarky jabs. Your criticism isn't digging deep enough in to these tools to even make much sense.