Re:21st Century C++
by olegkovalov on Tuesday February 11, 2025 @04:04AM
(#43010583)
> delivered in non-major versions
Can you clarify these 2 changes please? Cannot recall anything similar
Nope. It has been like five, maybe eight years, so I do not remember. There have been more since then, but after seeing how Google manages the Go project, I pay as little attention to it as I can possibly get away with... so I do not remember any details about them.
Re:21st Century C++
by olegkovalov on Tuesday February 11, 2025 @05:48AM
(#43011305)
> There have been more since then
Doubt, again. Without a minimal proof of mentioned problems continuing dialogue doesn't make sense for me, thanks.
$DAYJOB got burned badly twice on breaking Go behavioral changes delivered in non-major versions, so management created a group to carefully review Go releases and approve them for use.
All too often, Google's justification for breaking things is "Well, we checked the code in Google, and publicly available on Github, and this change wouldn't affect TOO many people, so we're doing it because it's convenient for us.".