syvolt
Joined 13 years ago
Joined 13 years ago
Definitely won't look as pretty as the parent project though but I prefer kong in terms of the actual code you need to write.
It will still add the dependencies of those tools as indirect dependencies to your go.mod file, that is what's being discussed.
I'm not a library author and I try to be careful about what dependencies I introduce to my projects (including indirect dependencies). On one project, switching to `go tool` makes my go.mod go from 93 lines to 247 (excluding the tools themselves) - this makes it infeasible to manually review.
If I'm only using a single feature of a multi-purpose tool for example, does it matter to me that some unrelated dependency of theirs has a security issue?
The anti-nuclear movement is also still alive and doing well but at this point it's like arguing over spilled milk, the damage is mostly done and a lot of is irreversible. We can try to salvage nuclear but we've already regressed to further impure sources in some countries so progress seems unlikely.
If you just try and imitate the average customer you will almost always be on the happy path, but ordering multiple books with multiple cards in a short period... I think that would trigger any decent fraud protection and not just at Amazon scale.