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/6493#issuecomment-1109892189,https://api.github.com/repos/pydata/xarray/issues/6493,1109892189,IC_kwDOAMm_X85CJ5xd,14314623,2022-04-26T14:48:33Z,2022-04-26T14:48:33Z,CONTRIBUTOR,"yes all of the grid methods (`grid.diff` etc) are now internally using grid_ufuncs. The axis methods are still going through the old code path, but will be deprecated soon! Please let us know how you get along with the new functionality, we are very curious for user feedback!","{""total_count"": 1, ""+1"": 1, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,1206634329
https://github.com/pydata/xarray/issues/6493#issuecomment-1102925385,https://api.github.com/repos/pydata/xarray/issues/6493,1102925385,IC_kwDOAMm_X85BvU5J,14314623,2022-04-19T17:49:55Z,2022-04-19T17:49:55Z,CONTRIBUTOR,"Hi @miniufo et al., just my two cents:

> This is simpler and do not make heavy dependence of the third-party package like xgcm.

That is a fair point, but I think there is a counterpoint to be made, that xgcm gives you some more functionality (especially with the new grid_ufuncs feature) with regard to array padding. As you note, this is not needed for your particular setup, but *if* you use xgcm, you would get the same functionality + at a later point you might get padding on complex grid topologies for free down the line. So in the end this seems like a tradeoff between adding more dependencies vs flexibility and generalizability in the future. 

> I'll give a try with differentiate() and pad() to implement grad/div/vor... But some designs in xgcm also inspire me to make things much natural.

This makes me think that you really want xgcm, because these properties will naturally be located on staggered grid positions, even if your data is originally on a A grid. And once you start to try to handle these cases it would appear to me that you duplicate some of the functionality of xgcm?

> I am still worried about the metrics concept introduced by xgcm. I think this should be discussed over xgcm's repo.

I second others here and think it would be great to elaborate on this on the xgcm issue tracker. But I also want to point out, that using the metrics functionality is **entirely optional** in xgcm, so if you desire, you can roll your own logic on top of grid.diff/interp etc. 

","{""total_count"": 1, ""+1"": 1, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,1206634329