That's a silly way of thinking.
* Define the problem to solve
* Look at potential solutions
* Pick one that fits
* Make stuff
Before you pick a solution (Language, framework, tool) you need to define the problem, because all solutions are better at and for some things than others.
So, what problem are you trying to solve?
Assembler, maybe not, but C++ makes perfect sense, in some cases.
And that's the problem.
You haven't specified what kind of problem you're solving, so it's almost impossible to suggest ideas.
It's kind of like saying "I want to build something, what tools should I buy?" (In regards to wood working).
I get tons of mileage out of ColdFusion, JavaScript, and Object Pascal. I make things for web, desktop, servers, GUI and cli, but you could do the same with PHP, TypeScript, and Java.
Or Nodejs, Dart, and Go.
I've used all of those in various combinations, and I gotta say that CFML + JS + Object Pascal is the most productive combo I've come across, but that's what's worked great for ME, and I only picked that stack after working with a whole bunch, and most of them professionally at some point.
Figure out what you want to build, then figure out what tools to use to make it.
The most important thing though, is that you start making stuff.
You won't "waste" time by learning Java/Nim/JS/Go/Pascal/TS/whatever, even if you end up switching languages later.
Programming isn't about memorizing syntax, it's about solving problems, creating solutions, and there's an awful lot that applies to just about any language once you get down to actually coding stuff beyond the basics.
Now go make stuff :)