Re:Comparison of C++17, Go, and Java for a next-generation s...
by movedx on Friday April 24, 2020 @12:04AM
(#22964501)
> Even in Go you gain performance by avoiding boxing.
Go has boxing?
> Because C++17 code if written well is likely to be much faster.
I was hoping someone could prove this, actually. I don't have the means or the knowledge.
Re:Comparison of C++17, Go, and Java for a next-generation s...
by magicalhippo on Friday April 24, 2020 @05:46AM
(#22966281)
> I was hoping someone could prove this, actually.
Maybe this presentation by Jason Turner from CppCon 2016 can illustrate just what can be done in C++17. His target in the presentation is a C64, but I think it illustrates well just what you can do with the language, and hence what tools are available for writing fast code.
https://www.youtube.com/watch?v=zBkNBP00wJE
edit: If you just want a quick fix, check out what a simple keyword does here: https://youtu.be/zBkNBP00wJE?t=1616
> If I can get the same work done in Go and I can learn Go in a week versus months for C++17 (which is far more complex), why would I pick C++17?
Because C++17 code if written well is likely to be much faster. If you don’t care about that, by all means stick with Go. But keep in mind that learning is a one-time cost, and you can keep applying the same knowledge to project after project.