This question is very hard to answer and really depends on your personal preference. And, to be honest (and blunt), it seems like your switching languages a lot and can't find a good language to settle down with. I know the feeling, but if your going to make anything big and major you can't really sprinkle lots of different languages in it because that makes the compiler (that is, the person who's building the project) need far more dependencies. For instance, if you mixed C#, C, C++, and Rust in a single project, you'd need .NET/.NET Core, all the packages (Nu or via assemblies) to satisfy .NET or .NET Core, a C compiler capable of compiling both C and C++, all the C and C++ libraries which you used, the Rust compiler, and all the crates you used when using Rust. This is a symptom known as 'dependency hell'. Dependency hell is a colloquial term for the frustration of some software users who have installed software packages which have dependencies on specific versions of other software packages.
The dependency issue arises around shared packages or libraries on which several other packages have dependencies but where they depend on different and incompatible versions of the shared packages. If the shared package or library can only be installed in a single version, the user may need to address the problem by obtaining newer or older versions of the dependent packages. This, in turn, may break other dependencies and push the problem to another set of packages. Unlike the dependency hell described here where the user gets frustrated, the builder also runs into this problem; they have to build libraries, compilers, programs and tools, which may need other libraries, programs, tools, etc., and so on and so forth, until your building so much that you run out of disk space or you enter a dependency loop and go no further, which only causes a massive mess that you cannot recover from. I would highly advise that you find a language your comfortable with first, program in it for a few months, if not a few years, look up code examples, research it, and then start doing big projects in it. Only then will you alleviate this problem permanently. But if you interbreed multiple languages together, your *going* to run into dependency hell, whether you like it or not. .NET/.NET Core does not have this problem only because the different CLI/CLR languages can be safely mixed because assemblies are language-agnostic. You have clearly rejected C# in favor of others and, therefore, will not have this safety resolver.
"On two occasions I have been asked [by members of Parliament!]: 'Pray, Mr. Babbage, if you put into the machine wrong figures, will the right answers come out ?' I am not able rightly to apprehend the kind of confusion of ideas that could provoke such a question." — Charles Babbage.
My Github