All those folks telling me to update my dependencies, this is why I don't do it. It's not laziness, it's undeniable foresight.

▲

beej71 2 hours ago | parent | next [-]

As long as your versions don't have any security issues...

▲

rirze an hour ago | parent | prev | next [-]

There's a reasonable solution to this. Tools like `cargo-audit` can tell you if a crate has security issues and guide you towards an update. You don't have to blindly update all dependencies this way.

▲

pixl97 2 hours ago | parent | prev | next [-]

I mean, yes, update your dependencies. But probably after a week or so after they've been release and tested by the first penguins willing to jump into the ocean.

	▲	kmeisthax 2 hours ago \| parent [-]
		Holding periods for new updates are a good idea, but I would also prefer having a tool that could provide diffs of the entire project state pre- and post-update; including transitive dependencies being added or removed. Git diffs won't show you that information, by design.

▲

abbadadda 2 hours ago | parent | prev [-]

What purpose does “undeniable” serve here? This tips over into hyperbole, in my opinion, whereas “it’s foresight” is much simpler and stronger. YMMV.

▲

pluralmonad 2 hours ago | parent [-]

I think it was to make the tongue-in-cheek nature of the comment more apparent.

	▲	jfklgkdkdnn 2 hours ago \| parent [-]
		That’s undeniable.