Yes. And it is a good idea. I have moved between Java backend applications and C++ videogames jobs. The difference in language and domain keep things interesting, and you discover that also there is a lot of sharing and you can apply patterns across very different domains. I have around ten years of experience in each.
I have also developed professionally in Clipper, Visual Basic, C# and even a little assembly. But, nothing for so many years as C++ and Java.
> Keeping up with framework churn should keep you busy for the next 25 years.
Oh. Yes. I just find it boring. To learn to do the same thing again and again with different named functions losses its appeal after a while. I try to keep my knowledge close to the core of the frameworks and google anything more complicated than that. I suck at interviews where I get questions about how to do this or that in a concrete version of a concrete framework, thou.
Java and C++ application programming are almost identical.
(Well, Java is a subset of C++/. CC++ is just Java plus extra work because you don't have the convenient shortcuts that waste CPU and RAM. There are many interesting novel languages for different problems .
> Keeping up with framework churn should keep you busy for the next 25 years.
I find it tedious. It's the same thing in a different way. The hot new framework doesn't do anything fundamentally different from the old framework. It's change but not improvement.
Yes. And it is a good idea. I have moved between Java backend applications and C++ videogames jobs. The difference in language and domain keep things interesting, and you discover that also there is a lot of sharing and you can apply patterns across very different domains. I have around ten years of experience in each.
I have also developed professionally in Clipper, Visual Basic, C# and even a little assembly. But, nothing for so many years as C++ and Java.
> Keeping up with framework churn should keep you busy for the next 25 years.
Oh. Yes. I just find it boring. To learn to do the same thing again and again with different named functions losses its appeal after a while. I try to keep my knowledge close to the core of the frameworks and google anything more complicated than that. I suck at interviews where I get questions about how to do this or that in a concrete version of a concrete framework, thou.