News for hackers. Stuff that matters.
Re:Go 1.17 is deprecating the traditional use of 'go get' by slver on Friday June 25, 2021 @10:35AM (#27631294)
Platforms that are not willing to deprecate parts of themselves in order to spur innovation and keep complexity low, eventually get deprecated as a whole.

Look at Java, the king of BC, even they've started deprecating packages in the JDK for removal.

It's inevitable. Otherwise it's like a brain that can't forget even the most useless piece of information. About an organism that just eats, but can't expel the waste.

There's a way to do change slowly, gradually and reasonably, but change is inevitable. If you don't want small changes, big changes will come for you.

Re:Go 1.17 is deprecating the traditional use of 'go get' by superkuh on Friday June 25, 2021 @11:22AM (#27631923)
No one is arguing for no change. The problems here are the new single corporation languages from this past decade that behave like 6 months is a long time. It isn't. Every ~4 years is more the cadence of everything before.
Re:Go 1.17 is deprecating the traditional use of 'go get' by jodrellblank on Friday June 25, 2021 @01:07PM (#27633513)
HN person a few days ago: "It's pretty common that I have to deal with support issues that were fixed six months ago, but the client has never taken an update in all that time..." - https://news.ycombinator.com/item?id=27492147

I was surprised to see six months described as "never, in all that time".

Re:Go 1.17 is deprecating the traditional use of 'go get' by rightbyte on Friday June 25, 2021 @12:25PM (#27632860)
Ye I understand that, but from a DevOp or system admin perspective all these small things adds up. 6 months deprecation is way too short to first realize this is changing and then fix all the scripts - and most likely still keeping backwards compability with older Go versions in the scripts for projects stuck in older versions.

The remedy in practice is pinning versions by project or even worse org. wide to be able to concentrate on the actual problem being solved if things are breaking too much.

Re:Go 1.17 is deprecating the traditional use of 'go get' by icholy on Friday June 25, 2021 @03:31PM (#27635233)
No one is forcing you to update.
Re:Go 1.17 is deprecating the traditional use of 'go get' by cesarb on Friday June 25, 2021 @12:32PM (#27632999)
> Look at Java, the king of BC, even they've started deprecating packages in the JDK for removal.

There is a reason plenty of organizations are still on Java 8, which is the last major release before they started doing that...

Re:Go 1.17 is deprecating the traditional use of 'go get' by kaba0 on Friday June 25, 2021 @05:41PM (#27636613)
They have only removed packages that was quite literally not used by anyone after being deprecated for years (deprecation doesn’t break compatibility).

The reason 8 is preferred for many is due to a) not understanding the new model b) depend on a dependency that does some shady things with JVM internals it should have never done in the first place, this did get “sealed” by the module system. Most of these deps actually have already migrated to 8+, and even if not, access to internals can still be allowed with a command line flag.

Re:Go 1.17 is deprecating the traditional use of 'go get' by slver on Saturday June 26, 2021 @04:26AM (#27640163)
Java 8 is not when they started doing that