issue_comments: 405743746
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/issues/2289#issuecomment-405743746 | https://api.github.com/repos/pydata/xarray/issues/2289 | 405743746 | MDEyOklzc3VlQ29tbWVudDQwNTc0Mzc0Ng== | 6213168 | 2018-07-17T22:05:29Z | 2018-07-17T22:05:29Z | MEMBER | Thing is, I don't know if performance on dask.dataframe is fixable without drastically changing its design. Also while I think dask.array is an amazing building block of xarray, dask.dataframe does feel quite redundant to me... |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
341355638 |