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/7344#issuecomment-1351908915,https://api.github.com/repos/pydata/xarray/issues/7344,1351908915,IC_kwDOAMm_X85QlH4z,1217238,2022-12-14T18:24:04Z,2022-12-14T18:24:04Z,MEMBER,"I think it's OK to still require bottleneck for `ffill` and `bfill`:

1. There are no numerical concerns: these functions simply repeat numbers forward (or backwards).
2. There is no good alternative to using a loop, and writing the loop in NumPy would be probitively slow.","{""total_count"": 2, ""+1"": 2, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,1471685307
https://github.com/pydata/xarray/issues/7344#issuecomment-1336299057,https://api.github.com/repos/pydata/xarray/issues/7344,1336299057,IC_kwDOAMm_X85Ppk4x,1217238,2022-12-04T01:55:34Z,2022-12-04T01:55:34Z,MEMBER,"The case where Bottleneck really makes a difference was for moving window statistics, where it uses a smarter algorithm than our current NumPy implementation, which creating a moving window view.

Otherwise, I agree, it probably isn't worth the trouble.

That said -- we could also switch to smarter NumPy based algorithms to implement most moving window calculations, e.g,. using `np.nancumsum` for moving window means.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,1471685307