issue_comments: 525425560
This data as json
| html_url | issue_url | id | node_id | user | created_at | updated_at | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| https://github.com/pydata/xarray/pull/3258#issuecomment-525425560 | https://api.github.com/repos/pydata/xarray/issues/3258 | 525425560 | MDEyOklzc3VlQ29tbWVudDUyNTQyNTU2MA== | 6213168 | 2019-08-27T18:26:17Z | 2019-08-27T18:26:17Z | MEMBER | @shoyer let me rephrase it - apply_ufunc is extremely powerful, and when you need to cope with all possible shape transformations, I suspect its verbosity is quite necessary. It's just that, when all you need to do is apply an elementwise, embarassingly parallel function (80% of the times in my real life experience), apply_ufunc is overkill. The thing I have against the name map_blocks is that backends other than dask have no notion of blocks... |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
484752930 |