@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"
Top-level
@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" 1 comment
|
@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