>>106920823 (OP)
I would recommend Go for "current year". I found C++ stifling and outdated, with inbuilt tools centered around making silly 90s tier applications like desktop clocks that nobody cares about. I really enjoyed the language but when it came to "okay now I'll make something" a blank void washes over you. "Just make de-bloated versions of existing programs!" is the general advice of what to make with C++, so you're making redundant tools that will suck compared to the real deal because you aren't going to maintain them as a full time job. Likely you will make something, it's stable, it does what you need, and just sits there unchanged for years as a result until you need a new feature.
I learned how much of a relic C++ is when I discovered that your options for actually having a cool windowed application people can use are limited to Qt or GTK. I thought there'd be insane amounts of GUI tools and there aren't, because it's ancient. I think back in the day there was VisualBasic or something. Otherwise people had to code their own windows etc, which they did because they were working in large teams of people where someone would be focused solely on producing that.
Rust is a good and modern language which is also packaged with things that actually matter for anything you will actually want to do. Not just making alarm clocks or weather app slop, but moreso interacting with the web, filesystems, etc. I would recommend Rust also, but for a solo dev, Go has an almost INSTANT build time, so if something goes wrong you can litter Printf throughout the failed function and find within seconds exactly what is wrong. Faster than AI or tracing through each function etc. and easier to come back to after a long time away.