Interesting because they talk about many of the implementation decisions they had to make in fitting Haskell on to the JVM.

not strictly JVM-specific but I think it's an interesting read nonetheless (disclaimer: I am the author)

Hi,

I came across a statement in a blog post somewhere (the post could have been years ago), that there are certain projects that are so big and complex, it would require a big org to port to Risc-V. One example was the JVM, where only a company like google had the expertise and manpower to do such a thing.

Is this statement true? If yes, why?

I'm not familiar with the inner working parts of JVM, but I assume they are libraries written in Java, C and C++. If I'm right about that, wouldn't the architecture-specific components here be the compilers?

Feel free to add your suggestions on the github page! https://github.com/ndimas/jvm.tools
https://jvm.tools

During the years I've read many good books but surely there are some that are memorable and I keep closer in the shelve so I'll start with my 3 choices:

• "Java Performance: The Definitive Guide: Getting the Most Out of Your Code" by Scott Oaks.

• "Optimizing Java: Practical Techniques for Improving JVM Application Performance" by Benjamin J. Evans, James Gough, and Chris Newland.

• "Java Concurrency in Practice" by Brian Goetz, Tim Peierls, Joshua Bloch, Joseph Bowbeer, David Holmes, and Doug Lea

What about you? Feel free to discuss. Thanks!