> If Bootsnap is an opt cache I'm all for it. It does integrate with the ISeq API in recent MRIs to acts as an opt-cache yes. It's not what brings most of the

> If Bootsnap is an opt cache I'm all for it. It does integrate with the ISeq API in recent MRIs to acts as an opt-cache yes. It's not what brings most of the performance gain though. > If it's some sort of `require' and `require_relative' hackage black-magic jiggery pokery then no. Well, there is no black magic, it's computers, they are machines, not magicians. And yes it's mostly what Bootsnap (and bootscale before it) does. > Bootsnap needs to be 100% bullet-proof before I go near it. The thing is it can't. There is a couple corner cases in Ruby's require semantic that just can't be replicated. So yeah, there is about a few dozen obscure gems out there that will break if used with Bootsnap, but for the vast majority of projects it's gonna be a drop in boot time gain without any headache.