Mike Bostock

That was more a note to myself re. tests. But I’d probably use vows (which is a little long in the tooth but I haven’t bothered to learn a replacement...

Another small optimization is using [d3.geoStereographicRaw](https://github.com/d3/d3-geo/blob/b95307a0bed0767155c717cc7ad0a022d6dfbe8d/src/projection/stereographic.js#L5-L8) (or inline the definition) instead of d3.geoStereographic.

Wow, nice example!

Maybe worth adding [logspace](https://numpy.org/devdocs/reference/generated/numpy.logspace.html) and [geomspace](https://numpy.org/devdocs/reference/generated/numpy.geomspace.html) too, while we’re here?

I don’t think the positional arguments with defaults are appropriate here because they aren’t analogous to Python’s named arguments. For example in Python you would say stuff like ```python np.linspace(2.0,...

My concerns here: * Too many positional arguments (start, stop, count, base) * Other implicit dependencies on base 10 (e.g., 2 and 5 are factors of 10, and 10 appears...

Sounds interesting? I’d love to see a sketch of what these might look like. Perhaps some combination of *array*.flatMap and d3.group?

I’ve dropped 1 and 2a into Observable notebooks for easy tinkering: https://observablehq.com/d/41bc065377cb7e36 https://observablehq.com/d/7021f34babd6fbf6

If I were to write the relig_income example in vanilla JavaScript, I’d probably use *array*.flatMap like so: ```js data.columns.slice(1).flatMap(income => data.map(({religion, [income]: count}) => ({religion, income, count}))) ``` Here’s another...

@nachocab Can you enable link sharing on the notebook so we can see?