Michael Niklas

Do you think that you can get it to work with static typing?

Is it not possible to have a CI run with ARM and S390x architectures? Maybe that would be a good improvement.

I think that the reverted y-axis is intentional. Imshow is intended to display images which have the origin at the top. xarray tries to keep the origin at the bottom...

See discussion in https://github.com/pydata/xarray/issues/6749 Maybe the current implementation of sum is not correct?

> What happens when you call a ufunc with an empty axis tuple? This should also happen with all other ufuncs then? I guess most of them just work, like...

I think that changing the behavior of sum is quite a large breaking change.

Another option is to add an option: `missing_dim`: "raise", ignore" or "broadcast". The default then would be ignore, which is the current implementation. But for workflows of variables that are...

Useful for debugging: `python -X importtime -c "import xarray"`

I think we could rework our backend solution to do the imports lazy: To check if a file might be openable via some backend we usually do not need to...

I just checked, many backends are importing their external dependencies at module level with a try-except block. This could be replaced by `importlib.util.find_spec`. However, many backends also check for ImportErrors...