Motivations to use @visx/scale instead of d3-scale directly

[jportela]

I'm trying to understand what @visx/scale offers on top of d3-scale.

By looking at the docs and examples, @visx/scale is widely used instead of d3-scale, so I'm assuming that's the recommendation (as opposed to using d3-array directly instead of a hypothetical non-existent @visx/array).

Looking at the source code, it looks like a wrapper on d3-scale, mostly to improve typings, as well as exporting a few utils that don't look that complex. Of course, I'm probably missing something important, and that's why I'm asking :)

Thanks!