The Modern Java Platform – 2021 Edition
jamesward.com
The Modern Java Platform – 2021 Edition
1–10 of 259 posts
Re: The Modern Java Platform – 2021 Edition
#2Re: The Modern Java Platform – 2021 Edition
#3Re: The Modern Java Platform – 2021 Edition
#4Re: The Modern Java Platform – 2021 Edition
#5GraalVM truly has the potential to become the universal, interoperable VM. It would be rational for e.g Julia folks to migrate to the graalVM ecosystem and cotntribute to it instead of living on their small code island. They would get an un inimaginable amount of benefits in the process.
Re: The Modern Java Platform – 2021 Edition
#6GraalVM truly has the potential to become the universal, interoperable VM. It would be rational for e.g Julia folks to migrate to the graalVM ecosystem and cotntribute to it instead of living on their small code island. They would get an un inimaginable amount of benefits in the process.
Re: The Modern Java Platform – 2021 Edition
#7Re: The Modern Java Platform – 2021 Edition
#8What does modern mean in this context?
> Non-blocking / reactive is one of the central demarcating elements of “modern” vs traditional.
Re: The Modern Java Platform – 2021 Edition
#9GraalVM truly has the potential to become the universal, interoperable VM. It would be rational for e.g Julia folks to migrate to the graalVM ecosystem and cotntribute to it instead of living on their small code island. They would get an un inimaginable amount of benefits in the process.
How does a VM (JVM, GraalVM) compare to something like LLVM's IR? From your description as a ``universal, _interoperable_ VM`` it seems like they have some similar goals --- what are the reasons to write a compiler to a VM instead of with LLVM/IR?
Re: The Modern Java Platform – 2021 Edition
#10My biggest gripe with java is developer productivity. It has gotten better but is still far behind interpreted languages like Python and Ruby. Class hot loading and things like that have made it better, but if you change a method signature or interface you have to stop your process, recompile, redeploy, and restart. For big codebases it’s brutal compared to the aforementioned languages and their attendant frameworks.
If you have huge codebase in Python or Ruby, you'll rip your hair more often because it's riskier to make changes (dynamic language) according to your use-case :).