2 ms·
It's not just that it's cheating, it's that it's less portable as well. A self-contained script can be thrown anywhere. One that needs a library needs to have t
by vacri 13y ago
It's not just that it's cheating, it's that it's less portable as well. A self-contained script can be thrown anywhere. One that needs a library needs to have the library taken with it. One thing that 'sysadmins' encounter than 'programmers' don't is a wide variety of systems with a varied install base. The more portable your coding, the easier time you have as you progress.
Throw in that programmers work on more monolithic projects, getting the libraries for those is (kind of) a one-time affair, but with sysadmins working on smaller, multitudinous projects, you can end up with a raft of different libraries to manage.
The real answer, as always, is 'be appropriate'. Often libraries are called for, but sometimes they're to be avoided. It depends on the use case, or even the library itself (we're currently using an abandoned one in production... and there's some crossing-fingers going on as we don't have the resources to fix it if there's breakage...)