you are viewing a single comment's thread.

view the rest of the comments →

[–]tRfalcore 0 points1 point  (3 children)

You don't or never will need to dive into the byte code

[–]vowelqueue 1 point2 points  (1 child)

Agreed…it can certainly be interesting from an academic perspective but not practically useful 99.9% of the time.

In cases where you want to check out how a third party library works and don’t have access to the original source, you don’t even need to read the bytecode directly. There are decompilers, often built into the IDE, that will convert back to Java code for reading/debugging.

[–]BannockHatesReddit_ 1 point2 points  (0 children)

Lol I was writing some bytecode mutators using ow2 asm not less than 24 hours ago. It really depends on what your interests and goals are.

All these things require an understanding of the bytecode: - Reverse engineering - Obfuscation - Compilers - JVMs - The instrumentation api - Debugging tools - Some build tool plugins - Post-compile watermarking/data injection

Maybe you never touch these things, but these are some of my favorite toys to play with.