3 ms·

Except that the JVM didn't take over all of programming (as some predicted back in the late 90s/early 2000s). C, C++ and Rust are popular programming languages

Except that the JVM didn't take over all of programming (as some predicted back in the late 90s/early 2000s). C, C++ and Rust are popular programming languages today. Probably because Java isn't a good systems language, or the ideal for all embedded tasks. And that tons of widely used code is written in C/C++.

szundi 3y ago
Let’s assume then that there is no GC for parts of the code. It’ll be constantly regenerated
- xboxnolifes 3y ago
  > It’ll be constantly regenerated What do you mean by this?
  - vrighter 3y ago
    probably a misunderstanding of what the GC is and does. The GC works on data, not code.
    - staunton 3y ago
      I think the generous meaning would be an experience like Rust (handles memory allocations/deallocations, doesn't mess up unless you really mess up) except that it doesn't complain all the time when you're doing "ok things" and maybe even makes it impossible in practice to mess up. It could even dynamically decide between using a GC for a given program or not, depending on what makes more sense (thus "constantly generating it").
pjmlp 3y ago
Mostly because Java did the mistake to gate AOT behind commercial licenses, thus C and C++ kept being relevant for many tasks requiring AOT workloads. Had Java shipped a AOT compiler in the box for free, Go would not happened, nor many of the workloads that Go has been taking away from C and C++ on the distributed computing space and devops. C and C++ would have their use cases reduced to kernel programming, embedded, games and like else.