I've never gone into the JVM itself, but I followed a course computer systems which gave me an idea how a VM works.
Another one:
machine code --> x86-64 --> C --> browser --> JavaScript --> ES6 --> EmberJS (it uses a vm as its rendering engine)
I've noticed that companies don't care though. They simply care about whether I have enough JavaScript experience. For me, personally though, it made me a lot calmer when solving bugs since lower level bugs are (usually for me) much more of a pain than bugs in JavaScript.
Usually, I read papers and blogs of tech companies.
Not those famous magazines like Ars Technica or Engadget, but Red Hat, IBM, Microsoft, AWS, Cloudera (yes I'm a system engineer).
3 comments
[ 2.8 ms ] story [ 19.3 ms ] threadmachine code --> x86-64 --> C --> virtual machines --> JVM --> Java
I've never gone into the JVM itself, but I followed a course computer systems which gave me an idea how a VM works.
Another one:
machine code --> x86-64 --> C --> browser --> JavaScript --> ES6 --> EmberJS (it uses a vm as its rendering engine)
I've noticed that companies don't care though. They simply care about whether I have enough JavaScript experience. For me, personally though, it made me a lot calmer when solving bugs since lower level bugs are (usually for me) much more of a pain than bugs in JavaScript.
If you want to figure this path out, I'd recommend https://www.nand2tetris.org/