4 ms·
I don't know about go, but java is pathetic. I have 30 years old c++ programs that work just fine. However, an application that I had written to be backward co
by thbb123 2y ago
I don't know about go, but java is pathetic. I have 30 years old c++ programs that work just fine.
However, an application that I had written to be backward compatible with java 1.4, 15 years ago, cannot be compiled today. And I had to make major changes to have it run on anything past java 8, ~10 years ago, I believe.
- simoncion 2y agoCompared to C++ (or even Erlang), Go is pretty bad. $DAYJOB got burned badly twice on breaking Go behavioral changes delivered in non-major versions, so management created a group to carefully review Go releases and approve them for use. All too often, Google's justification for breaking things is "Well, we checked the code in Google, and publicly available on Github, and this change wouldn't affect TOO many people, so we're doing it because it's convenient for us.".
- olegkovalov 2y ago> delivered in non-major versions Can you clarify these 2 changes please? Cannot recall anything similar
- simoncion 2y agoNope. It has been like five, maybe eight years, so I do not remember. There have been more since then, but after seeing how Google manages the Go project, I pay as little attention to it as I can possibly get away with... so I do not remember any details about them.
- olegkovalov 2y ago> There have been more since then Doubt, again. Without a minimal proof of mentioned problems continuing dialogue doesn't make sense for me, thanks.
- simoncion 2y agoKek.
- pjmlp 2y agoAs long as you are lucky enough to not have used any stuff dropped in C++14, C++17, C++20 and C++23. Exception especifications, gets, GC, string ABI,...