At first glance, this question sounds defiant, almost taboo, the hackneyed answer often pops up to it, that everything is subjective and depends on the task. Is it really?
Returning to logic and common sense, we will try to identify the most objective criteria for comparing programming languages. Who is not afraid to be disappointed when they see their favorite language stigmatized and betrayed by shame , let's venture to speculate which is better for industrial development?
Selection principles
There are many ecosystems, it is stupid to start with the selected advantages of one, so we will act by exclusion on clear points. All comparisons are based on objective benchmarks .
Maintainability
First of all, the language must be mainstream enough for the project to be supported. We immediately throw overboard all the exotic and functional things like Haskell, Elixir, Nim, Erlang ... the dying Ruby to the same place. For the same reason, we discard all kinds of languages of closed (Swift) and even more so pupated according to the passport (1C for example) ecosystems.
Typing
General practice in the industry shows that weak typing definitely hurts readability, maintainability and generates a large number of errors, so we throw out JavaScript and PHP. Further, we note that dynamic typing degrades the speed of work , and the compilation options for traditionally dynamic languages are poorly maintainable, and look more like a perversion attached to the side with crutches, so strongly typed, but dynamic Python and TypeScript are left out.
In the dry residue
, -- C#, Java, C++, C Kotlin, Go Rust. ( ) C++ , , , .
Java vs C#
C# Java . . Java , , . C# , Java ( , , List
). .NET .
Kotlin
C# , ++. Kotlin , C# , . . C# , Kotlin "" . ? , , Kotlin . Kotlin, , C# , - Java.
Go?
Rust?
Rust C++, C++ , . Rust - , (!) , , C++.
. . !
, , , Kotlin, C++ . Kotlin , Android , JS WebAssembly , iOS, jpackage Windows, macOS, Linux "" .