Tom Nicholas

So I don't think that making this change would make much difference to code portability in practice, because: - It only applies to local files (there's no such thing as...

> we will still need the `fs_root` argument, because some pre-existing kerchunk files come with only relative paths. Actually could this just be a kwarg to the kerchunk parsers?

Just chiming in with a vote in favour of this feature - the ability to symbolically manipulate cloud-like paths without assuming we actually want to access data at those paths...

> Is it not installing dependencies? Is it guaranteeing no network calls? Both ideally. The context is a codebase that stores and manipulates bucket paths and prefixes across a range...

I just ran into this - it's very ugly. I'm surprised that all stores do not have a root group by definition?? This also makes it impossible to use `.tree`...

I personally think that's a bad design choice, and that there should always be a root group. But I understand that that is a spec-level problem. Separately I would still...

> am having second thoughts about whether this is worth adding to the API. Something like this interface > `Store.get_size(key: str) -> int` would be very useful for virtualizarr, as...

This sounds frustrating 😕 > Writing "to_zarr" on a lazily loaded dataset or datatree reference should, in my opinion, actually read the data contents and write it to the new...

@shoyer did you see https://github.com/pydata/xarray/issues/10622? I raised that issue to discuss the general problem of how these libraries interact with each other when it comes to concurrency. > I'm pretty...

> OK, let's try to reach some initial resolution about the async strategy for Xarray over in https://github.com/pydata/xarray/issues/10622 first! My understanding of that issue is that people thought that it...