Go 2 For "Breaking With The Past" Will Never Come

[phoronix]

Phoronix: Go 2 For "Breaking With The Past" Will Never Come

An update on the Go programming language roadmap was shared today that highlights some recent improvements for backward compatibility to Go and why the developers now no longer expect to ever have a "Go 2" release that would break compatibility with existing Go 1.x programs...

https://www.phoronix.com/news/Go-Language-Roadmap-No-2

[coder]

"The window for Go 2 quickly went away?"

"The window for Go 2: already gone?"

Oh, the potential for puns is rather delicious.

[qlum]

This is a good thing, While there are definitely costs with staying compatible really is an important quality to have. It allows everyone to move forward and prevents a lot of headaches and needless work migrating. The pain that is the python 2 to 3 migration comes to mind, as do the many breaking changes in php.

[Healer_LFG]

They'll just make a new language and call it something other than "Go 2" when they need something that requires them to break compatibility

[cl333r]

This is a good thing, While there are definitely costs with staying compatible really is an important quality to have. It allows everyone to move forward and prevents a lot of headaches and needless work migrating. The pain that is the python 2 to 3 migration comes to mind, as do the many breaking changes in php.

After Go adopted generics it was clear to me Go 2 will never happen.

But I'd still like a Go 2 to fix the little core issues, like I want "i64" as in Rust, not "int64", project management is shitty compared to Rust... Rust does a lot of stuff better.

[Zeioth]

I've never used frameworks from a company with so many breaking changes as Google. Every year, something has to be rebuilt from scratch due to semantic changes (not even new features)

[cynic]

Maybe my favourite Go feature: my code never breaks after a language update.

[cynic]

I've never used frameworks from a company with so many breaking changes as Google. Every year, something has to be rebuilt from scratch due to semantic changes (not even new features)

this might be true for most Google products, but not for Go.

[IActuallyKnowItAll]

C++ 2 in the making, then. No breaking changes, slow cruft buildup. In 10 years we will cry for breaking changes but it will be too late.

[coder]

How about "Go2 considered harmful", after Dijkstra's 1968 foundational paper (link) , which gave us functions instead of assembly-spaghetti

Nice. Post of the day, if not the week!
🤣