Skip to content

Comment on Ruby Under a Microscope: Learning Ruby Internals through Experimentparent

Comments

Hey thanks for asking - and yes, in the preface to the book I do explain how I figure this stuff out. But basically I: - study the C code for a long time - step through it in GDB a lot - add printf statements and recompile it to print out debug/trace info - actually change it to see what would happen if things were written differently.

A lot of hard work! I do the hard work so you don't have to :)

Your process is something I'd like an ebook or screencast about. Perhaps others would find it interesting as well.

Yea I've thought about that. Let me see what I can do... :) thanks.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.