Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> main issue is with the Java zealots

Any sufficiently large population will have someone who will literally say anything. And the common outrage trope on the internet is to rage against a straw man.

Now I haven't used GraalVM in production, but in having played around with it and doing new code from scratch, I found AOT compilation to be really good.

I think the change will come faster than you think.

You can build your leaf, domain level code into a native shared lib and still use the reflective code at the top level to compose the application.

https://www.graalvm.org/reference-manual/native-image/#build...

If Java gets CTFE (compile time function evaluation), constexpr for C++ folks, much of the need for runtime reflection would disappear.

There is no reason that JITed reflective code (along with VM) can't be combined AOT code in the same program. You can already do this in Graal via front ends for llvm-ir and wasm.

As it is now, you can already mix Rust, C, C++ trivially with bytecode via LLVM ir. And for languages that compile to Wasm, GraalVM has a front end for that as well.

https://www.graalvm.org/reference-manual/wasm/#embedding-web...




If Java gets CTFE (compile time function evaluation), constexpr for C++ folks, much of the need for runtime reflection would disappear.

Just to remind people that Quarkus has a "pre-compile" stage that allows code to wire itself up using reflection, annotations, config properties, etc, before the full compile. This makes start-up times much faster.




Consider applying for YC's Fall 2025 batch! Applications are open till Aug 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: