Dean Jackson

@Joey10582 @Scobleizer @cly3d @AdaRoseCannon There are a lot of features in USD that are not in glTF (for good reason). It's not a competition where only one format will win. Also, Apple is implementing WebXR, in Open Source.

@Scobleizer @cly3d @AdaRoseCannon I know. Annoys me to no end. For such a major player to pick sides like that early on is disappointing to say the least

@AdaRoseCannon Yaaaaayyy!!!! I have adult supervision in the VR/XR groups at last! Welcome Ada.

@hybridherbst @mrdoob @threejs This is fantastic. Is this online anywhere yet or a WIP?

Oh look @mrdoob, straight outta @threejs into QuickLook 👀(in wonderful debug colors 🎨) #madewithneedle #screenshotsaturday

@mrdoob @smfr @alexanderdanilo That's true. For many years there was meme-like advice of "want something to be fast? throw a 3d transform on it".

@smfr @grorgwork @alexanderdanilo Maybe it would have been better to do a more explicit API for offloading to the compositor. Using CSS3D for video integration only makes sense to the people that deeply understand how browsers work. I bet 95% of web devs don't know what offloading and a compositor is.

I've tried to be open minded about <model> but the latest spec discussions are making me lose any hope.

@kmcurry @mrdoob @TanayDimri @SebAaltonen Hopefully the owners of USD also see the Web as an important use case. We're definitely pushing for it.

@kmcurry @mrdoob @TanayDimri @SebAaltonen Honestly, I'm not sure! There are lots of great features in USD that would be useful on the Web. But, at the same time, it's heavy (as you mentioned) and infinitely extensible (which is sometimes good, but makes interoperability hard).

@mrdoob @smfr @alexanderdanilo There has been a lot of investigation/documentation into how to get good performance out of 2D transforms. 3D (as @smfr said, really 2.5D) should be the same. I admit that you see a lot of bad designs that use 3D transforms. There are also some complications with CSS layout.

@smfr @alexanderdanilo @grorgwork What other applications were made with it? Web devs are confused about what to do with it because it's very easy to use it badly and get bad performance out of it.

I can't find the tweet now, but someone suggested <model> was a way to own the Metaverse. 1. If you wanted to own something why would you try to develop it as an open standard that works with other technologies? 2. I don't know what the Metaverse is.

@mehmetoguzderin @w3c @Litherum @DaKangz @kainino0x @dneto1969 Congratulations! Well deserved.

It is a moment of privilege to share that I became an official editor of @W3C WebGPU Shading Language today. I want to take a moment to thank people who enabled me @Litherum @grorgwork @DaKangz @kainino0x @dneto1969. As a person born in 2000 with Dystrophic Epidermolysis Bullosa,

@mrmaxm @mrdoob I'm familiar with the Web :)

@grorgwork @mrdoob Designing API - been done before. The hardest part is taking into account web-specific 3D requirements and UX: streaming, async loading, content optimization, infinite number of unimaginable use cases of API (configurations, galleries, games, scroll-pages, *orn, etc).

@mrmaxm @mrdoob @TheJare @threejs @playcanvas @babylonjs Please read the explainer and referenced tweets where we explain why we don't "just use WebGL".

@grorgwork @mrdoob @TheJare @threejs @playcanvas @babylonjs - they already do that, and much much more!

@mrdoob @alexanderdanilo I can answer this one!! CSS Transforms was a way to give a very simple CSS-based way to do compositing in Web layouts (i.e. accelerated rendering). Once you do that, the 3D implementation comes basically free, and allows for some nice designs (with care).

@alexanderdanilo @grorgwork What was CSS3D created for?

@arturitu @mrdoob Are you saying we'd want to turn off canvas? No way. <model> isn't trying to compete with canvas at all. Canvas will always be more powerful - a black box that allows you to do anything!

@mrdoob If <model> takes shape, it seems that in a while we will see an open letter published titled "thoughts on canvas"

@mrdoob @TanayDimri @SebAaltonen Yep. USD needs a lot of improvements to be well-suited for the Web. It's very popular as a powerful interchange format/API between DCCs, but not as good for final mile delivery to a browser.

@TanayDimri @SebAaltonen It's indeed a hard sell to force every browser out there to include the USD SDK.

@mrmaxm @mrdoob It's definitely the hardest part - how to expose an API that isn't overwhelming (both to developers and the specification), balanced with giving something useful. (The other hardest part is compatible rendering)

@mrdoob I believe, having more in-depth requests and discussions on things like: animations, illumination, camera, IBL, consistency, assets streaming, async loading, video textures, audio, interaction between <model> elements ... It will just overload the spec to the point it will fail.

@mrdoob @TheJare That's true in the initial proposal, but it's about taking small incremental steps. Step 1: Plonk a 3d object in a page Step 2: Expose some API to control cameras, animations, and maybe register event handlers Step 3: Expose the scene graph

@TheJare Oh yes, definitely.

@warrenm @mrdoob Hi Warren! I'd like to hear more about what level of abstraction you think would be right. We've tried to explain why we aim at this level, but probably haven't done a good job.

@mrdoob It has been, from the moment of its conception, obviously the wrong level of abstraction, and a magnet for terrible implementations. It should be relegated to the pile of terrible ideas, and then further iterated on, in the open, and with full input from a broader community.

@alexanderdanilo @mrdoob We go into it a bit in the explainer, and in the following tweets: twitter.com/samweinig/stat…

@mrdoob Well <canvas> was only created for OS X dashboard widgets. <model> is probably for some other product idea that will come to light eventually. Apologies to @grorgwork if my interpretation is wrong

Reminder: @samweinig explained a lot of the thinking behind <model> here: twitter.com/samweinig/stat…

@mrdoob Oh no!! :( I'm very happy to talk to you to get your thoughts and feedback!