Hacker News Reader

Comment by barelysapient | Hacker News Reader

This just got me. Datadog decided that they only support the current and last major versions of Go. So, 1.26 and 1.25. But in my cause we're still on 1.24.13 which was released by the Go team less than two months ago.

Datadog won't be getting a renewal from us.

View on HN

> But in my cause we're still on 1.24.13 which was released by the Go team less than two months ago.

Yes, and then one week later the entire 1.24 branch entered EOL: https://endoflife.date/go

So upgrade to 1.25? What reason could you possibly have to be so far behind?

I can understand staying one version behind latest, to not be exposed to brand new bugs, which do happen, but staying two versions behind is pointless.

Using a release less than two months is hardly “so far behind”. The 1.24 series had considerable regressions that have taken a number of patch releases to fix, it stands to reason that the same would be true of newer releases. Given there's still miscompilations getting fixed as late as 1.25.8, and 1.25 brought in large changesets for the new experimental GC, sticking it out while 1.24 is still getting patches a mere handful of weeks ago is not unreasonable.

Heavily regulated industry with a lengthy change control process for this sort of thing.

Personally, I love all of the new Go stuff and I'm using the current version on my personal projects.

What hacks are you relying on that makes it impossible to upgrade to 1.25 or even 1.26?

Does it even matter?

Reply on news.ycombinator.com