Korijn van Golen

There is definitely a learning curve, for sure! But it's not very steep. I think the first step should be to step up our documentation game. The API is already...

> Hi, this is something I may be interested in helping to develop and it's stirring a bit of interest in the local neuroscience community over here! The compatibility with...

Thanks for sharing your thought process here, it helps us understand better what you're thinking of when reading this issue. I am immediately reminded of issue #188. Perhaps we should...

I think `Multiple views with independent cameras (a la arbiter)` is available now right?

You're right, it's all supposed to be managed and tracked as part of the renderer. But we don't have to fix this right away.

This is implemented now right?

It's still baffling to me that we can't just set an option on the WGPU pipeline to only render the lines (I think it's the "fill mode"?). That's how every...

Also see https://github.com/m-schuetz/webgpu_wireframe_thicklines which also seems to use readonly storage buffers :/

Can I help with anything? Maybe I can prepare a PR for wgpu-py: > Add support for aarch Linux in wgpu-native and wgpu-py (and test on a rpi).

Looks like this is going pretty smoothly so far?