A Pragmatic Guide to Choosing Your Language (and Workplace)
Description
This is a screenshot of an online Q&A post, likely from a site like Quora. The question at the top is, "Which language is best, C, C++, Python or Java?". The answer, provided by Andrea Ferro on January 7, 2015, gives a breakdown of use cases for each language. It recommends C for operating systems, C++ for high-performance applications, and Python for rapid development where speed is less critical. The punchline comes with the final point: "If your boss told you: 'do it in Java or you are fired' I suggest you use Java and look for a better workplace." The humor resonates with senior developers by playing on a common stereotype of Java (especially around 2015) as a verbose, often mandated language in large, bureaucratic enterprise environments that developers might not choose freely. The advice is presented as pragmatic and reasonable until the final jab, which turns it into a commentary on workplace culture and developer autonomy
Comments
7Comment deleted
The post is from 2015. An update for today: the advice for C and C++ is the same, Python is what you use when time to market is key until you hit the GIL, and Java is now surprisingly good but you're probably still stuck on version 8 from the last decade
C when the silicon is the API, C++ when nanoseconds affect revenue, Python when marketing already put the demo in the slide deck, and Java when you’re really just integrating with the org chart
The four stages of language enlightenment: C for when you need to talk directly to the metal, C++ for when you need objects but still care about nanoseconds, Python for when you realize developer time costs more than CPU time, and Java for when you realize your mortgage costs more than your principles
The real architectural decision framework: C for when you need to count every cycle, C++ for when you need to count every cycle but with classes, Python for when you need to ship before the heat death of the universe, and Java for when you need to update your résumé. The most honest language selection criteria is often 'what keeps the lights on while you interview elsewhere' - a reminder that sometimes the most critical technical debt isn't in the codebase, it's in the org chart
Java: where the JVM's warmup time matches your sprint to update the resume
The only decision tree that optimizes for Amdahl's Law right up until Conway's Law throws a checked exception
C for things that boot, C++ for things with microsecond SLAs, Python for things that must demo Friday, Java for things that must survive procurement