I rewrote some charting code at work using this approach, and the benefit really shines through when you're already working with a React codebase. You can basically add most of what D3 can do for you without introducing a separate DOM manipulation paradigm. It doesn't really matter which way of doing it is better: two different ways of doing it are definitely worse.
If you're already a D3 expert or you have a bunch of existing D3 graphs you want to plop into an existing app, sure, you can use the ref approach. But if you want modular, reusable React components to build out an application, the approach Amelia outlines here works great.