3 ms·
Don't forget "Requiring automatic dynamic memory management ("garbage collection") is several orders of magnitude less efficient than letting developers use sta
by aidenn0 14y ago
Don't forget "Requiring automatic dynamic memory management ("garbage collection") is several orders of magnitude less efficient than letting developers use stack and manual memory management"
This is kind of like saying "Writing in FORTRAN is several orders of magnitude less efficient than letting developers use assembly" yes, a smart enough engineer can write assembly that is, at worst, no slower than FORTRAN (proof by fact that FORTRAN compiles to assembly). But this doesn't mean that on real-world projects FORTRAN won't win.
- jonathansizz 14y agoThe article was claiming that C++ failed in the 90s with the large migration from C++ to Java; it 'failed' at being the general-purpose industry language of choice. This is a reasonable statement. And Java is often 1-2 orders of magnitude less efficient at memory usage than C++, so while 'several' is perhaps hyperbolic the general point still stands (execution speed wasn't being discussed).
- aidenn0 14y agoJava is not the only runtime with automatic dynamic memory management. I could run comparisons against "tcc" and conclude that java is an order of magnitude faster than C.
- spitfire 14y agoAda actually has the sane memory management by default compared to both C++ and Java. Pointers are, by default verboten. Pointer arithmetic will generate a compiler warning. People should genuinely look into this stuff more rather than just dismissing it offhand. Ada got almost everything right for a procedural-OOP language. It was just too far ahead of its time.