> If Go 2 won't break Go 1 programs, shouldn't it be Go 1? Yes, that's what the ... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		mseepgood on Aug 14, 2023 \| parent \| context \| favorite \| on: Backward Compatibility, Go 1.21, and Go 2 > If Go 2 won't break Go 1 programs, shouldn't it be Go 1? Yes, that's what the article is saying.

unethical_ban on Aug 14, 2023 [–]

Ah. So to phrase it differently,

"There will never be a Go 2 unless marketing says we should renumber."

Just stop referencing "Go 2" as if they ever think it will exist, then!

metaltyphoon on Aug 14, 2023 | [–]

Agreed. It’s confusing as hell

Consider applying for YC's Summer 2026 batch! Applications are open till May 4
Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact