|
Top-level
 @darius Web standards change all the time and people still use ancient browsers that don't support them, so people build their own "standards" as libraries which try to account for all of this...which is cool in theory except these web dev libraries seem to rise and fall just as often as the standards they're trying to replace....IMO, in the end you often just trade one big, constantly shifting pile of bloat for another... TL;DR: 2 comments
@darius Yup! On the one hand, computing is entirely built upon layers of abstraction, "use the library" is a very core concept of software engineering. On the other hand...some libraries ultimately aren't providing much abstraction in the end, and you've gotta balance that against the additional resource consumption, the loss of control, the effort of learning the library....a lot of libraries feel to me like they're merely a fraction of a true abstraction layer and therefore not worth it |
Gregory's Server
@admin right, that's the thing! I used to be a "use a library, the library will update so I don't have to" and that is just... almost never true in practice. I've come back around to "at least my own code was written by me so I can fix it"