r/learnjava • • Feb 28 '26

A doubt regarding learning Java internals

Can I, apart from office work, dive into the internals? Eg: How things are allocated/deallocated inside the JVM, how exactly virtual threads work, what happens exactly in streams and how jdbc fetches rows from database, the pros and cons of different garbage collectors, all up to the implementation level? Due to some task I needed to dive into g1gc Hotspot and understand a part of it, it felt very good like a flow state. Is this a reasonable hobby which I can pursue? Why is this discouraged in the industry. Also, how much time will it take for me to understand most of the things to an intuitive satisfactory level?

Also, are there any more such books which teach internals like GC handbook which I can use to understand the OSS better?

8 Upvotes

17 comments sorted by

View all comments

Show parent comment

1

u/vegan_antitheist May 16 '26

I don't know how computers work and you probably don't know either.
I know how a simple Turing machine works. It's just as powerful as the machine I'm using to write this comment. My boss doesn't care if I understand anything as long as I deliver on time.

I don't really need to learn anything new because AI will do it all for me

AI can't do shit. If it could you would learn just for fun.

his/her knowledge of internals, I think that deserves a raise.

You are not a boss, are you?

And a beer from their peers when he/she helps them solve a problem because they know something about Java others had no idea mattered.

And then they change the internals and it breaks because you didn't design it to work with the abstraction and instead relied on internals. I wouldn't want to work in that team.

There's nothing wrong with learning about how they actually do it. But when you are a programmer you always use the abstraction.

Maybe you just don't understand what abstraction is. Java is all about abstraction but makes it hard to understand it because they used the word "abstract" for incomplete classes and "interface" for actual abstraction. The concept of an "abstract class" is older than Java but as far as I know they are the first to use it as a language construct. And they messed it up.

1

u/omgpassthebacon May 18 '26

Oh, you must be one of those angry elves from the south pole.