We are literally talking about a kind of amnesia and generational gap in knowledge transfer here. I was there for VRML.
You could almost make a 2022 business model redoing already solved problems and pretending you are inventing new solutions.
Technology doesn’t always linearly progress, sometimes later solutions are technically worse than older ones due to “don’t care” optimization values or lost knowledge or purely social or political reasons. There are also trade offs like portability-performance etc, I’m not denying, but IMO much web “innovation” is useless generational churn and busywork… to say nothing of humans trends and groupthink.
Starting fresh could easily be the reason it's failing again because much time is wasted in reinventing the wheel.
The problem is still the use case not the tooling.
You could see a future though where you go into one portal and you're in Minecraft, and you go into another and you're playing tennis with your buddy in Europe. Games would just be new portals -- the key here is that it's hosted by different companies, not Meta.
I came away with the distinct impression that people really don't want to admit that XML is good enough.
For complex object description it excels - as anyone who has used a complex UI description language knows, the 'lite' Json, yml, insert hipster conf file format here face a myriad of problems in description that they only somewhat make up for in simplicity.
It is the flaw of misattributation of Occams rule to everything - simplicity is indeed efficient but it cannot account for complexity, and the world ends up a complex place.
"3d in a browser" sounds like a fairly broad use case. Three.js is fairly popular I hear.
> If your 3d format can do NURBS it can do anything.
If your 3d format can do NURBS, it can theoretically given unlimited CPU and memory _display_ anything. But that doesn't mean that it can communicate with other devices over the network with low latency. Or can effectively transmit new objects - or people - in your vicinity over the network fast enough to interact with them - especially if arbitrary detail is important, think about a doctor looking into a patient's ear. Or represent moods, emotions, feelings, etc., or even sounds. We don't even know if smells or tastes are next!"If only WWW would have charged to make a link...."
Maybe with good reason: If it didn't take off last time maybe there are hidden stumbling block in the specification. Trying fresh might unconsciously bring the right ingredients this time. There is the faint possibility that specification and implementations were correct, just too far ahead of its time and infrastructure; it's usually worth taking this risk though. And of cause reinventing means owning and deeply understanding.