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

Except Go certainly is never getting another major version, I am waiting for Go 1.10000.0, given how decisions are made on the ecosystem.


What's wrong with Go 2 with tools to automate migrations? Of course that limits the scale of possible changes, but moving methods between packages should be possible with this approach.


Community culture, most likely it will never happen as such.


Change doesn’t have to come at the pace of npm. Let’s be charitable, people. :)




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: