Sometimes I get shocked by these numbers and it reminds me how little I know about business. Like if you showed me the wikipedia page for Zapier and asked me give it some value, I would be way off. Or if you pitched the business idea to me, I would tell you do something better with your time.
It will be around for a long time. This shouldn't be a reason not to pick up C++.
> I‘m currently part of a team that needs help with C++ development.
That might be a good sign that you should pick it up but the details matter a lot. Getting to the point where you're productive with C++ in an existing codebase takes a while even for people who are experienced with the language let alone someone who is just learning it. So I would invest the time to learn C++ for work only if it's a long-term project where you'll have the necessary support from the rest of the team and from your engineering management. You need to establish the expectation that you can't just jump in and immediately make meaningful contributions. If it's a case of "this old C++ repo runs a critical piece of our product and we need a person to make some changes and maintain it", then stay as far away as possible.