Wrapping Up 2021. Leaving C++
21–30 of 251 posts
Re: Wrapping Up 2021. Leaving C++
#22Re: Wrapping Up 2021. Leaving C++
#23Makes me wonder if I've too strongly tied my career to a specific language. However, right now it's not that I'm specifically a C++ programmer, just that the industry (gamedev) is largely C++. I'm sure in for it if that shifts out from under me before I find stable employment though....
E.g. colleagues of mine who have only used Python have no idea about references, heap and stack, L1/2/3 caches and so on. It's a shame.
Re: Wrapping Up 2021. Leaving C++
#24Makes me wonder if I've too strongly tied my career to a specific language. However, right now it's not that I'm specifically a C++ programmer, just that the industry (gamedev) is largely C++. I'm sure in for it if that shifts out from under me before I find stable employment though....
The C++ programmers will just switch to C++ 2.0, aka Rust. It's not a big leap.
Re: Wrapping Up 2021. Leaving C++
#25Re: Wrapping Up 2021. Leaving C++
#26Makes me wonder if I've too strongly tied my career to a specific language. However, right now it's not that I'm specifically a C++ programmer, just that the industry (gamedev) is largely C++. I'm sure in for it if that shifts out from under me before I find stable employment though....
If you don't know web stuff you should learn web. There was a time I would say every programmer should know C. Today I would say JavaScript.
Re: Wrapping Up 2021. Leaving C++
#27Re: Wrapping Up 2021. Leaving C++
#28[flagged]
Re: Wrapping Up 2021. Leaving C++
#29I'm sorry but these are such superficial problems. I don't need overloading (arity or otherwise) since Rust kind of has overloading thanks to the traits.
Variadic generics might be necessary since C++ doesn't have a good macro system. But Rust does so you achieve it that way.