4 ms·
My question is: if you can code in C++, why should you write C++ on top of GraalVM instead of going native (and faster)?
by mister_hn 6y ago
My question is: if you can code in C++, why should you write C++ on top of GraalVM instead of going native (and faster)?
- zelly 6y agoBecause Java is much cheaper in terms of development time and HR
- mister_hn 6y agowell I disagree with this. You can waste a lot of time, especially in the debug phase, due to runtime errors not caught at compile time
- Jataman606 6y agoDebugging Java is easier than C++ though.
- pjmlp 6y agoBecause to code in C++ with the safety of Java, specially in distributed computing scenarios, I have to make people go through this. https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines https://docs.microsoft.com/en-us/cpp/code-quality/?view=vs-2019 https://docs.microsoft.com/en-us/cpp/code-quality/?view=vs-2... And most of the time is a lost battle to force people to change, so it is easier to bring in people that have other culture towards security when plugging software into the network. As for GraalVM support for LLVM, that is mostly for language interoperability purposes.
- hokkos 6y agoBecause is my case Java is the only language with libraries that implement all the rare needs I have. And because I need to create an application with the smallest memory footprint possible. And in my best attempt at it, I use a Rust Webserver that use a static GraalVM compiled Java library containing all the business code thus eliminating the fat Java http/web libs, so I have a lower exe footprint that translate is smaller memory footprint because executable are loaded in memory at one point.