How to Choose a Programming Language? A Rational Look at the Truth Behind Language Selection

Does Choosing a Programming Language Really Determine Your Destiny?

"Your language choice is your destiny" — this phrase circulates widely among beginner programmers, sending countless newcomers into a spiral of anxiety. Should you learn Java, Python, Go, C#, Rust, or dive into the AI/algorithm track? In this episode from Coder Group on Bilibili, the hosts take a high-level perspective and arrive at a thought-provoking conclusion: In theory, anyone can choose any programming language.

This might sound simple, but it cuts straight to a common misconception in the tech world — the idea that programming languages exist in a strict hierarchy, and that picking the "right" one means winning while picking the "wrong" one means losing from the start. This article unpacks the rational logic behind language selection based on that core insight.

The Core Principle: No Programming Language Is Inherently Superior

One principle the hosts repeatedly emphasize is this: there is no such thing as "one language being inherently more advanced than another." Those with a scientific mindset should approach this question rationally and probabilistically, rather than getting swept up in the online "language snobbery" narrative.

Regardless of whether your background is a vocational college, undergraduate, or postgraduate degree, China's massive software market can accommodate practitioners across virtually every language specialization. The hosts offer several telling examples: many people claim "PHP is dead," yet a quick search on any job board reveals plenty of companies still hiring PHP developers. Even languages considered "obsolete" — like Cobra or Pascal — still have job postings.

This phenomenon follows a clear pattern in the history of programming languages. The TIOBE Index — one of the world's most authoritative programming language popularity rankings — has tracked over 150 languages since 2001. Its data shows that even languages ranked below 50th place still have tens of thousands of active developers worldwide. PHP, born in 1994, has been "declared dead" countless times, yet still powers roughly 77% of server-side websites globally (including the entire WordPress ecosystem). Pascal, designed by Niklaus Wirth in 1970 as a teaching language, lives on in embedded systems and industrial control applications. This historical pattern reinforces the article's core argument: the market is large enough, and demand is diverse enough. A language being "niche" vs. "mainstream" doesn't translate directly to "jobs exist" vs. "jobs don't exist" — it's a difference in probability, not a binary outcome.

Three Core Dimensions That Differentiate Programming Languages

If no language is objectively superior, what actually sets them apart? The hosts identify three key dimensions: probability, difficulty, and growth potential.

Probability: Mainstream Languages Mean Broader Opportunities

Choosing a mainstream language like Java, Python, or Go means you can most likely find relevant job openings in cities across the country. With a niche language, many cities may have no matching positions at all — not zero in absolute terms, but far less probable.

It's worth noting that these mainstream languages differ significantly in their technical positioning, and understanding those differences leads to more informed career decisions. Java has long been the backbone of enterprise backend development thanks to the JVM's cross-platform capabilities; the Spring ecosystem is mature and widely adopted by major Chinese internet companies. Python's clean syntax and rich scientific computing libraries (NumPy, Pandas, PyTorch) make it the go-to choice for data science and AI, though it has performance limitations in high-concurrency scenarios. Go, released by Google in 2009, natively supports concurrency via goroutines, compiles fast, deploys simply, and has risen quickly in cloud-native and microservices architectures. Rust is known for memory safety and zero-cost abstractions, challenging C++ in systems programming — but its learning curve is extremely steep. When choosing a language, understanding the applicable boundaries of its technical ecosystem matters far more than simply comparing "popularity scores."

Growth Potential: Balancing Opportunity and Competition

Mainstream languages generally offer greater room for career growth, but there's a trade-off: where growth potential is higher, competition is also fiercer. Conversely, niche languages may have a lower ceiling, but the competitive pressure is often much lighter. This is a decision that depends heavily on personal circumstances — there's no universally correct answer.

Difficulty: Entry Barriers and Advancement Thresholds

Different languages and different tracks vary significantly in how hard they are to break into and how steep the path to mastery is. This dimension becomes especially relevant when discussing whether to switch tracks.

Already in a Niche Track — Should You Switch to a Mainstream Language?

This is a real dilemma many developers with some work experience face: "I chose a niche language early on — should I switch to a mainstream direction now?"

The hosts' answer: Not necessarily. It depends on your specific situation.

This judgment maps onto two important concepts in economics: the Sunk Cost Fallacy and opportunity cost. The Sunk Cost Fallacy refers to the tendency to continue a course of action because of resources already invested (time, money, energy), even when the expected future returns no longer justify it — "I've spent 3 years learning PHP, I can't let that go to waste" is a classic example. A rational decision framework should only consider future opportunity costs: how much time would it take to rebuild your competitiveness in a new language? Generally speaking, developers with 3–5 years of experience have a relatively manageable transition window. But for a senior engineer with 10+ years under their belt, the architectural thinking, project experience, and industry connections they've accumulated are often far more valuable than the language itself — the marginal return from switching languages could actually be negative.

Key factors to weigh include:

• Time cost: Switching tracks may not be feasible in time; learning a new language and rebuilding your experience base requires a significant time investment.
• Switching cost: If the cost of changing direction is too high, staying the course and seeking other growth paths within your current specialization is often the more pragmatic choice.

Being in a niche language track doesn't mean there's no room to grow. Career paths are multidimensional — your programming language is just one variable, not a verdict on your destiny.

Using Probabilistic Thinking to Evaluate Extreme Cases

To make the core logic of "probability" concrete, the hosts offer two representative examples.

Case 1: A vocational college graduate going into Java backend development. This is genuinely competitive, but only in a probabilistic sense. Does it mean they absolutely can't make it? Not at all. Maybe there's a 10% chance of success — and you could be in that 10%.

Case 2: A high school student becoming an AI algorithm engineer. This is the more extreme example. In roughly 99% of cases, it won't work out — and this barrier exists for solid technical reasons. AI algorithm engineers (especially in research-oriented roles) typically require deep mathematical foundations: linear algebra (matrix operations are the mathematical essence of neural networks), probability theory and statistics (Bayesian inference, maximum likelihood estimation), calculus (backpropagation is fundamentally about chain-rule differentiation), and convex optimization theory. At top internet companies, more than 80% of applicants for algorithm roles hold master's degrees or above, typically from 985/211 universities in computer science, mathematics, or statistics. That said, AI deployment engineers (MLOps, model deployment, AI application development) are fundamentally different from pure research roles — they demand stronger engineering skills and have a comparatively lower barrier to entry. This is the real-world basis for the hosts' caveat: "what if there's a 1% chance you're a genuine prodigy?"

The key takeaway from both cases: every choice is a matter of probability, not an absolute binary judgment. Understanding which probability range you're operating in and making rational decisions accordingly is far more valuable than spiraling into anxiety over "picking the wrong language."

Closing Thoughts: Rational Thinking Is Worth More Than Language Anxiety

Circling back to the original provocative question — "your language choice is your destiny." After this analysis, it's clear that statement is far too absolute. Your choice of programming language does affect the distribution of opportunities, the difficulty curve, and your growth ceiling. But it's more like a game played across different probability ranges than a verdict handed down by fate.

For beginners, starting with a mainstream language gives you the broadest coverage of opportunities. For those already established in a niche track, there's no need to blindly follow trends and switch directions — instead, weigh the time costs, switching costs, and your personal development goals together.

What the tech world truly needs is not the anxiety of being enslaved to a "language snobbery hierarchy," but the rational, probabilistic thinking that a scientific mindset demands. Getting clear on what you want and what you can handle matters far more than endlessly debating "which programming language is the best."

Key Takeaways