Trying to clear some misjudgments about Go, the programming language (or any tech stack) among newcomers

There seems to be some misjudgment about Go as a programming language for newcomers as well as seasoned devs, and I just want to address it for the sake of my mind (I am tired of reading these discussions across the developer-verse, incoming rant).

Once a language becomes mainstream, it will be applied wherever it's suitable. Engineers who are building products now in comparison to decades ago when Java/.NET came out (20 years for both) will have another tool to choose from, so they WILL potentially use it. Go was introduced almost a decade ago, which is a long enough time for people to try it and build shit, Newcomers who picked it up during or after that time (knock-knock 2008-9) have now probably become Senior Engineers/Founding Engineers/CTOs, so these folks will eventually make it part of their long term stack if they want to, ultimately requiring you 🫵🏽 to learn it, because plenty of codebases have been written by these early adopters, and they have to be maintained.

Go is not an "alternative" to pick when someone has magical scale problems with Java, it's a tool, just like Java itself, built to write code, push to prod, and get shit done. Go markets itself as being fast yes, that's one of its selling points, but it's still a "general-purpose programming language", and it will be used as such, for "general purposes", whether your product has a scale of 20 users or 20 million.

How fast is it?, Whether it's better than XYZ because of ABC, shouldn't matter to you as a user (difference scenario if you are a contributor), especially not if you are new to the industry, and it also shouldn't matter to experienced fellas as well until you have squeezed all the performance out of your current stack. This of-course doesn't mean you shouldn't know about those things, it means that the cost of migrating a 10K LOC codebase written in another language to any other lang even if you have a faster alternative available, is not worth it. Some teams can choose to invest in it, and that's their choice not a consensus across the industry, that migrating to Go from some ABC lang will be worth it or not.

The line b/w writing performant applications is now very thin for all existing languages (this is a personal statement, I have no benchmarks, but I do see how all languages become better & faster every day, how people who build them are dedicated to making their ecosystem better.)

Now, whether you decide to learn it (Go) or not, whether you will get a job by learning it doesn't matter. Languages are not created to provide you with job opportunities, they are built to solve problems and change ways to solve things. That's it.

(Who TF am I? I have been writing Go for 3 years, A User)