Hello fellow developers and code newbies.
My name is Amir Bekhit aka Bek Brace, and the following is my honest opinion about what I think of the most famous question on twitter ...
Why Asking "Which Programming Language is Good or Bad?" is the Wrong Question
As developers, we often find ourselves in debates about which programming language is the best. But let’s be honest, asking "Which programming language is good and which is bad?" isn’t really helpful. Here’s why this question might be leading us astray and what we should focus on instead.
The Problem with "Good" and "Bad"
Labeling programming languages as “good” or “bad” oversimplifies a complex topic.
But I love Python! It's the best for everything, for automation, ML, DS, game dev, web dev, coffee making, and steak grilling ... "
, a drunk friend said
Each language has its strengths and weaknesses, and what works for one project might be a poor choice for another.
Here are a few points to consider:
- Context Matters: The right tool for the job depends on what you’re trying to achieve. Are you building a web app, a mobile app, a game, or a data analysis tool? Each domain has languages that are more suited to it.
- Personal Preference: What’s good for one developer might be frustrating for another. Some people love Python for its readability, while others swear by the performance of C++.
- Community and Ecosystem: The support and libraries available for a language can make a big difference. A “bad” language with a strong community and ecosystem can be more productive than a “good” language that’s less supported.
Choosing the Right Language for Your Project
*Instead of asking which language is good or bad, ask yourself these questions:
*
What is the Project Scope?
For quick scripts or automation tasks, Python might be the way to go.
For high-performance applications, consider C++ or Rust.
What is Your Team’s Expertise?
If your team is experienced in JavaScript, building a web app with Node.js or React makes sense.
If you’re all Java experts, leveraging Spring for backend services can speed up development.
What are the Project Requirements?
Need real-time performance? Languages like C++ or Rust could be beneficial.
Building a web frontend? JavaScript (or TypeScript) is almost unavoidable.
What Ecosystem and Libraries are Available?
Does the language have the libraries you need?
Is there a strong community for support and contributions?
Embracing a Growth Mindset
Instead of sticking to what we know and debating which language is better, let's embrace learning.
Each language can teach us something new and expand our thinking as developers. Here’s how:
Learn Multiple Languages: Understanding the basics of different languages can give you more tools to solve problems.
Focus on Concepts: Many programming concepts are universal. Learning them in one language can often transfer to others.
Stay Curious: The tech landscape is always evolving. Staying curious and open-minded can keep you ahead of the curve.
Conclusion
In the end, no programming language is universally good or bad, and as I said in the video, it's a vehicle that will take you where you want. It’s all about finding the right tool for the job and continuously learning.
By focusing on what languages can offer in specific contexts, we can make more informed decisions and become better developers.
So next time someone asks you, “Which programming language is the best?” tell them -> Amir said: "for which purpose?" then consider diving into a discussion about their project needs instead. It’s a more productive and insightful conversation.
Thank you for reading, hope this was useful, and I will catch you in the next one.
Top comments (4)
Every question is a good question to ask, if the goal is to learn from it. In this case, you could even write a clear piece of why you think it is a less good question to ask ;-)
I beg to differ. It's not a question of good or bad, it's a question of right or wrong, correct or incorrect. That's the message I'm trying to convey. But whatever makes you happy of course, it's just my opinion :-)
I'm not against what you wrote, but I know people can ask questions in a way that the receiver can't deal with.
If that's the case, it's up to the receiver what more information is needed to answer the question.
Got it , thank you for your insights 🙂, Marcelloh