3 ms·

Java and C++ are virtually fully backwards compatible. Java 1.6, 10 years old, is still commercially supported. C++ compiler support depends, but can go back fa

by fnl 9y ago

Java and C++ are virtually fully backwards compatible. Java 1.6, 10 years old, is still commercially supported. C++ compiler support depends, but can go back far, too. Golang only seems to support the latest two [minor] versions, however (so, 2 years, maybe). I don't see how Go's long-term support is in any way outstanding. And, we still need to see what happens when Go moves to version 2...

cratermoon 9y ago
See The Go 1 Compatibility Promise[1]. Something programmed in Go 1.5 still works in Go 1.10 1. https://golang.org/doc/go1compat https://golang.org/doc/go1compat
- fnl 9y ago
  What part of my statement makes you think I said anything to the contrary of that?
  - cratermoon 9y ago
    > Golang only seems to support the latest two [minor] versions, however (so, 2 years, maybe). Go 1.0 was released 28 Mar 28 2012. Go is on a six-month release cycle[1]. Focusing on the number of minor versions is not only the wrong thing to do (because different languages release updates at different rates) but it's also factually incorrect, because by schedule, 2 minor releases happen in a year. 1 https://github.com/golang/go/wiki/Go-Release-Cycle https://github.com/golang/go/wiki/Go-Release-Cycle
w8rbt 9y ago
The other nice thing about C++ is that you can specify which standard you want to use -std=c++11, etc. when compiling. I hope AWS Lambda supports C++ someday too. Anyway, I like Go too and agree it's very stable and while it's not as formal as C++ (ISO standards) it's been very stable. Give it 10 years to know for certain.
barsonme 9y ago
Go's lack of commercial support for previous versions is a non-issue. There's generally little reason why you can't just bump to the next minor version number. Go's 1.x promise means any code written for 1.1 will work on 1.9 and so on.

3 ms·

Java and C++ are virtually fully backwards compatible. Java 1.6, 10 years old, is still commercially supported. C++ compiler support depends, but can go back fa

by fnl 9y ago

cratermoon 9y ago
See The Go 1 Compatibility Promise[1]. Something programmed in Go 1.5 still works in Go 1.10 1. https://golang.org/doc/go1compat https://golang.org/doc/go1compat
- fnl 9y ago
  What part of my statement makes you think I said anything to the contrary of that?
  - cratermoon 9y ago
    > Golang only seems to support the latest two [minor] versions, however (so, 2 years, maybe). Go 1.0 was released 28 Mar 28 2012. Go is on a six-month release cycle[1]. Focusing on the number of minor versions is not only the wrong thing to do (because different languages release updates at different rates) but it's also factually incorrect, because by schedule, 2 minor releases happen in a year. 1 https://github.com/golang/go/wiki/Go-Release-Cycle https://github.com/golang/go/wiki/Go-Release-Cycle
w8rbt 9y ago
The other nice thing about C++ is that you can specify which standard you want to use -std=c++11, etc. when compiling. I hope AWS Lambda supports C++ someday too. Anyway, I like Go too and agree it's very stable and while it's not as formal as C++ (ISO standards) it's been very stable. Give it 10 years to know for certain.
barsonme 9y ago
Go's lack of commercial support for previous versions is a non-issue. There's generally little reason why you can't just bump to the next minor version number. Go's 1.x promise means any code written for 1.1 will work on 1.9 and so on.