defining a NumPy API standard?
I think this hits the crux of the issue... There is a huge coordination problem. Users want to move their code from NumPy to Sparse or Dask all the time, but it’s not trivial to do. And libraries like sparse and Dask want to follow a standard (or at least hoped there was one) before they existed. Maybe I think the issue is bigger than it really is, but there’s definitely a coordination problem. See the section in the original email on “who cares and why”... Best Regards, Hameer Abbasi
On Sat, Jun 1, 2019, 05:23 Hameer Abbasi <einstein.edison@gmail.com> wrote:
Those are big problems, but they aren't coordination problems :-) https://en.m.wikipedia.org/wiki/Coordination_game If you and I both each have our own unrelated code that we want to move to Sparse, then we don't have to talk to each other and agree on how to do it. -n
On Sat, Jun 1, 2019, 05:23 Hameer Abbasi <einstein.edison@gmail.com> wrote:
Those are big problems, but they aren't coordination problems :-) https://en.m.wikipedia.org/wiki/Coordination_game If you and I both each have our own unrelated code that we want to move to Sparse, then we don't have to talk to each other and agree on how to do it. -n
participants (2)
-
Hameer Abbasi -
Nathaniel Smith