3 ms·
Some people need to get with the picture and drop those antiquated 2021 practices. Puke!
by hbn 4y ago
Some people need to get with the picture and drop those antiquated 2021 practices. Puke!
- rcarmo 4y agoIt's a decent joke, but one of the reasons I only took up Go almost a decade after it got started was that I wanted to invest on a stable language ecosystem that wasn't after the fad of the week (like certain runtimes we all know). I'm actually looking forward to Rust having a few more years under its belt so I can do more than experimentation with it (and yes, I've seen the Oxide stuff, and there is plenty we can call stable right now -- I just want it to be a bit more weathered...).
- bryanlarsen 4y agoGo: started 2007, announced 2009, 1.0 2012 Rust: started 2006, announced 2010, 1.0 2015 The weathering on the two languages seems fairly similar. In fact it could be argued that Rust is more stable. Golang is talking about a breaking Go2, Rust has a fairly good forward compatibility story and plans.
- nindalf 4y agoI don’t think there’s any plan for a Go 2. I’m willing to bet we won’t see one in the next 10 years. The main feature that might have required breaking changes (generics) was introduced successfully without any breaking changes. Rust has no plans for 2.0 either. Both are stable languages that have been making steady progress.
- bryanlarsen 4y agohttps://zchee.github.io/golang-wiki/Go2/ https://zchee.github.io/golang-wiki/Go2/ https://www.youtube.com/watch?v=RIvL2ONhFBI https://www.youtube.com/watch?v=RIvL2ONhFBI
- mayormcheeseman 4y agoThe first link states that Go 2 is TBD and in the event there is a Go 2, interop must be easy. The second link has Rob Pike state that there probably won’t ever be a Go 2.