The difficulty is the number of people still running old versions, as soon as new iOS versions come out a super high percentage of people switch. And with browsers you have to account for the update cycles of every browser on the market.
This is super exciting for us as we develop interactive browser UIs. I hope future versions of WebGPU will be backwards compatible to all those with Chrome 113.
We need an iOS like pace of updating for browsers!
I've always struggled with Safari for it's terrible WebGL implementation. Even had to globally disable anti-aliasing otherwise the app would be unusably slow!
Thanks for your response, sorry to hear you moved away due to performance limitations.
We've been working hard to improve our performance/scalability for large models over the last couple of years. We shipped major updates in this area recently so I'd be interested to hear when you last used the tool.
I'd love to dig into what issues you had so we can make sure they're resolved for you/other people.
Thanks, great points. Especially the last one about it being difficult for an org to figure out who should be editors/readers/etc. It's definitely a challenge for us that we'll need to think more about.
We have ideas to increase the capability of readers to make edit suggestions, that can be accepted by an editor. This way you can have some of the more junior team members included in the reader count.
Looks super interesting, giving visuals some structure is super helpful especially when you have so much information to display. Helps make it navigable/digestable.