4 ms·
I generally tend to (perhaps superstitiously) do things the "slow way" like this, for exactly this reason. This kind of thing is also generally why I don't und
by nerdponx 5y ago
I generally tend to (perhaps superstitiously) do things the "slow way" like this, for exactly this reason.
This kind of thing is also generally why I don't understand people who don't like "dependencies" in general. If something requires specialized knowledge, I would much rather let the specialists work on it, than arrogantly assume I know enough to do it myself correctly.
- Jtsummers 5y agoThere are (at least) two kinds of dependencies: 1. Complex libraries and mechanisms that you couldn't (or are complex enough that you wouldn't) make on your own. 2. leftpad. The former is worth using in many situations. I would not make any kind of network protocol implementation myself in most cases because, while I can, I don't have time to do it correctly (vice hiring a proper expert or purchasing/using an expert made implementation). The latter is the garbage that causes problems, for various reasons. The ubiquity, for instance, of this totally trivial package broke a lot of other systems when they could have been replaced with a very small (and easily shown correct) bit of your own code. The other problem is that they are opportunities for corruption of your system. The more dependencies you have (direct or indirect via transitive dependencies) the more attack surface area (poor code permitting an attack) or potential for others to insert attacking code (the code isn't just insecure, but it's actually the attack itself).
- bobthepanda 5y agoThe problem with dependencies is that you start relying on Other People's Support, and that can vary from package to package. The support you get from the Apache Foundation is going to be a lot different than the support you get from, say, a React community-maintained fork of an originally JQuery component that builds some oddly specific finicky frontend paradigm.
- recursive 5y ago> If something requires specialized knowledge This seems to be very much the point. I suspect there's actually disagreement about whether the thing actually requires specialized knowledge. If there were actually 700 days of February 1295 in the Holy Roman Empire, what are the chances that month would be handled correctly by any layer of my Thursday-counting Saas platform? A lot of times the "specialists" are just as likely to say something like "Dates before 1900 are not supported because they're too hard". And your app probably didn't care about those cases anyway.