I am pretty proficient in C++ and Java. I know that most progrmas could be written in either language. My question for those of you who have been out there for a while, do companies tend to use one programming language for certain types of programs? For example, is C++ typically used for larger applications and Java used more for web based programs?

I tend to like working with Java more, but am not so interested in web development(seems a lot of Java jobs deal with using JSP and servlets). Do I need to choose the type of programming I want to do, then go with the language most widely used, or is it feasible to choose the language I want to work with and be able to get into the type of programming I want?

Dani AI

Generated

Short summary and context: the practical line most teams use is “pick the tool that fits the problem.” That echoes ’s advice to master a language and ’s point about who steers a project. Building on ’s hardware example and ’s original question: employers usually pick a language for domain, runtime constraints, existing code, and available libraries — not because one language is objectively “better” in every case.

Common mappings (what you’ll actually see in job postings):

  • C++ — systems, real-time and embedded code, game engines and performance‑critical libraries. (isocpp.org)
  • Java — long-lived back ends, application servers, and many enterprise systems (JSP/servlets and full Java EE stacks historically); Android moved toward Kotlin as the preferred language for new apps. (docs.oracle.com)
  • C# — Microsoft/.NET server and desktop work, cloud APIs, and Unity game scripting. (learn.microsoft.com)

Performance and tradeoffs: the old “Java is slow because it’s interpreted” line misses the modern picture. Production JVMs use tiered JIT compilation and adaptive optimizations (HotSpot), so long‑running server code often gets very close to native throughput. For short‑lived or startup‑sensitive apps, AOT/native-image approaches (GraalVM, etc.) can dramatically reduce startup time and memory use. For deterministic low‑level control or tiny runtimes you’ll still prefer C++. (openjdk.org)

Practical path (short checklist):

  • Choose a domain first (embedded/games, enterprise backend, cloud, mobile).
  • Build 1–2 small projects that mirror that domain (e.g., a C++ cross‑compiled embedded demo or a Java Spring Boot REST service).
  • Learn tooling: build systems (CMake / Maven/Gradle), debugging, profiling, and version control.
  • When job hunting, highlight domain experience and relevant libraries/frameworks — language fluency is valuable, but domain skills sell the role.

This complements the thread: you don’t have to “pick a language and be stuck” — pick a domain, prove it with projects, and the language skills will follow.

Recommended Answers

All 8 Replies

whether you choose java or you choose c++ ... do it at your best ... be a master.

Hi,

I cannot comment really on what the big development world uses, but I know I use C++ for accessing parallel ports / hardware in Linux, and use shell scripts to manage the file system.

I think a lot of your behind-the-scenes drivers are going to be C or C++ based. JAVA is interpreted, and that means slow down when running through the libraries.

Christian

I think it has a lot more to do with who is in charge of the project technically. People have preferences and they tend to go with what they like.

Being good at both is a good way to go to AN job.

Thanks for the replies. One more question, C#, how has that been doing in the busisness world? Is it becoming popular or is C++ and Java still the better way to go? Is it worth the time to learn it?

still C++ and Java r popular out there.

JAVA is interpreted, and that means slow down when running through the libraries.

Just to let you know, thats not true. Java is actually quicker than C++, since libraries are determined before its compiled. So once compiled, the library is carried with the program, unlike C, which has to determine after

Java is actually quicker than C++, since libraries are determined before its compiled. So once compiled, the library is carried with the program, unlike C, which has to determine after

almost correct. The real reason is that the bytecode compiler can create optimised code for every specific platform it may run on.
Java may LOAD slower than C++ (especially if you count JVM startup time) but once the program starts running there will not be a significant difference.
This is especially true for programs that spend most of their time waiting for user input.
What does it matter if your calculations take 10ms or 11ms if the application then has to wait a minute for the user?

if you send sum thing about c++ programming (how to use).

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.