3 ms·
None of the memory problems of C++, the speed of C++ most of the time. Thousands of high quality libraries, a JVM that is a marvel of engineering after 20 years
by belter 3y ago
None of the memory problems of C++, the speed of C++ most of the time. Thousands of high quality libraries, a JVM that is a marvel of engineering after 20 years, tooling for development, monitoring and introspection of exceptional quality. Many of the internal tools at the largest Cloud developed in Java. Most enterprise level software. NASA extensive use of Java. A team behind the development who has stunning common sense in resisting the latest fads. Support for IEEE 754 that took years. AOT compilation...The infra behind most internet banking sites out there. Use in high speed trading.
What else do you want from the ecosystem?
- hutzlibu 3y agoWhat would be a modern IDE for Java? I remember programming Java in Eclipse. And it was powerful for the time, but everytime I read bloated, I automatically think Eclipse since then..
- jayd16 3y agoIntelliJ is very good.
- belter 3y agohttps://www.jetbrains.com/idea/ https://www.jetbrains.com/idea/
- mdaniel 3y agoand also FOSS (Apache 2): https://github.com/JetBrains/intellij-community https://github.com/JetBrains/intellij-community (as well as PyCharm found in the "python" subdirectory)
- iddan 3y agoAnother rather new option is VSCode + the Java plugin
- hugi 3y agoEclipse has seen vast development in the last few years and is fast and easy to use these days.
- gabereiser 3y ago>” None of the memory problems of C++” I’m sorry, I’m calling BS here. You can still leak memory in Java.
- vlovich123 3y agoYou can leak memory in any language. That’s an impossible bar. The problems op is referring to is obviously about memory safety. Java obviously isn’t thread safe like Rust is, but it’s typically safer than C++ on that front too.
- gabereiser 3y agoRust isn’t thread safe either. It’s borrow checker will attempt to correct you but you can still run Rust unsafely.
- laurencerowe 3y agoAs I understand it Rust's unsafe is designed so you can encapsulate unsafety behind a safe interface. It's up to the programmer to verify the safety of code using unsafe. But it they do so correctly then you can rely on the borrow checker to verify that everything else is safe. This means that when you run into a thread safety bug in Rust code you should only have to look at the unsafe blocks to find the culprit.
- kaba0 3y agoWith that said, I think it is important to mention that if you go off the safe path in rust and you do hit such a bug, your current execution is no longer trustable, it could have corrupted the heap, introduce UB, and die with a segfault, etc. In java, race conditions can enter illegal application state, but their scope is much more limited. NPEs are 100% safely handled, etc. you can only get off the safe road with using Unsafe unsafe, and manipulating the JVM’s inner state which is not even allowed by default. Depending on application, this difference may matter a lot!
- 3y ago
- loxias 3y ago> None of the memory problems of C++ Every time I see something like this I roll my eyes... C++ doesn't have any "memory problems". There are sometimes human problems, such as thinking one is capable of coding without understanding the (basic programming) concept of a pointer. But that's because the human's dumb, not a language problem. (This argument also sometimes comes from those who do understand basic programming, but are only familiar with C++98.) > Thousands of high quality libraries a JVM that is a marvel of engineering after 20 years I reluctantly have to agree. :)
- inglor_cz 3y ago"But that's because the human's dumb, not a language problem." If everything is the programmer's fault for being dumb, then Brainfuck is an excellent system language.
- kaba0 3y ago> Every time I see something like this I roll my eyes... C++ doesn't have any "memory problems". You can choose which report you would prefer: Microsoft's, Google's 65%, ... I'm sure they just hired bad developers that don't understand pointers. Sure, human problem, but if no human can use the tool correctly, then surely there is some problem with it. And no, that doesn't mean that memory unsafe languages don't have a place, but we really should have a very good reason for going down that road.
- erik_seaberg 3y agoI understand pointers, yet I can’t be trusted never to make a mistake with them. “Each mistake will go uncaught and become an unpredictable catastrophe” is a language problem when your target audience is made of meat.
- grumpyprole 3y ago> C++ doesn't have any "memory problems" Well, every time I see someone claim this, I roll my eyes.
- segfaltnh 3y agoIt must be hard being perfect. The rest of us will keep looking for solutions for mortals.