4 ms·
"Java over Go" seems kind of weird. Go has been around for a decade and it seems like code built on 1.0 should still work, if you're not too crazy about depende
by skybrian 5y ago
"Java over Go" seems kind of weird. Go has been around for a decade and it seems like code built on 1.0 should still work, if you're not too crazy about dependencies?
- grey-area 5y agoYes it’s a terrible example directly contradicted by the graph he gives above of everyone stuck on Java 8. Go, after 10 years, is still on version 1 and likely to remain so and takes this problem of breaking updates really seriously.
- empthought 5y agoPretty sure that decision is based on the standard library size and package repository culture, not language updates.
- grey-area 5y agoAgain, those are reasons not to use Java vs Go. The Java standard library is a bit of a mess and far too large for human comprehension and personally I prefer the Go package culture of never breaking HEAD it has led to very stable builds IME.
- grey-area 5y agoIMO the Go libraries are less extensive but more focussed than Java and the Stalin covers most of the bases for web apps very well.
- Joeri 5y ago“Angular over react” is also a bad example because in my experience angular upgrades take more work and are necessary more often.