4 ms·
Hey, I wrote the original post. Though theoretically any interpreted language gives you all of this, you actually might not have access to the internals in pra
by rtpg 6y ago
Hey, I wrote the original post.
Though theoretically any interpreted language gives you all of this, you actually might not have access to the internals in practice. JS (well, node.js and browsers) doesn’t expose GC internals (partly due to a spec requirement that the language be deterministic), and barely gives you good exception introspection.
There is also the ergonomic advantage of no static typing: you just get a reference and can figure out the type later. Very useful when poking around unknown objects. I imagine an API like this in Java would be much more verbose and requiring a lot of casts etc.
- taeric 6y agoHaving taken a dive on some memory issues with Java, the tools that you have at your disposal are quite nice, actually. https://www.yourkit.com/java/profiler/features/ https://www.yourkit.com/java/profiler/features/ shows roughly what the memory charts look like. So, yeah, if your want is to inspect using the host language, I can see how this makes sense. That said, as you noted in the post, you really just want to get to the root asap. Which is why most visualizations will start from there. :D