It has to with some of the magic we're trying to do with Yaml serialization that works with the Syck API but we haven't spent the time to figure out what it would take to update it to work with Psych as well.

No, it really isn't. That got added as a response to a lot of bug reports we were getting. Since we're overriding #to_yaml (or was it .yaml_new?) on a couple core classes we would get bugs reported against DJ that were really poorly written config files in people's applications.

It's not a great fix. We've talked a bit about dropping some of the magic, and especially the monkey patching for DJ 3.0 while trying to maintain the public api.

It has to with some of the magic we're trying to do with Yaml serialization that works with the Syck API but we haven't spent the time to figure out what it would take to update it to work with Psych as well.

No, it really isn't. That got added as a response to a lot of bug reports we were getting. Since we're overriding #to_yaml (or was it .yaml_new?) on a couple core classes we would get bugs reported against DJ that were really poorly written config files in people's applications.

It's not a great fix. We've talked a bit about dropping some of the magic, and especially the monkey patching for DJ 3.0 while trying to maintain the public api.