3 ms·
> Could be more popular? The APIs are already there, literally nothing stops you from writing a pure js lib that supports 3d models in a way that you want and c
by sorenjan 5y ago
> Could be more popular? The APIs are already there, literally nothing stops you from writing a pure js lib that supports 3d models in a way that you want and can be reused on any site that needs it.
The APIs are there, but not the renderer or a way to interact with it. I'm looking at it as a consumer, not a web developer. I don't want to have to write a library or use someones else's, that's the point. Browsers have native video controls when embedding mp4 files with the video tag, you could argue that could be done just fine with html and javascript instead.
> video needed 3rd party plugins to even run. Video still managed to attract a sizeable user based before that.
Of course video attracts lots of users, that one of the main use of internet for many. Besides Netflix and similar streaming, looking at short clips on Facebook and Reddit is why a lot of users open their browser in the first place. Should everything that's not as popular then be dismissed? Should we not have svg support in browsers? Should video decoders be shipped as webassembly blobs? Should we do like Google docs and render the whole page in a canvas tag?
> Of course I am all in favor of dropping Chrome for Unreal I think the later doesn't call home half as much.
Unreal uses Chromium Embedded Framework, so all you need to browse the web is the Unreal Engine and a build environment, and you can make your own web client. No need for extra browsers.
- josefx 5y ago> I'm looking at it as a consumer, not a web developer Then why do you care if it is part of the browser or just a library? A consumer doesn't need to know that, certainly wont interact with a model element directly. > you could argue that could be done just fine with html and javascript instead. Not at the time the video controls where introduced and now many sites use DRM which would prohibit a pure js implementation unless you want to piss of Netflix, Amazon, etc. . > Should everything that's not as popular then be dismissed? There are finite browser developers working with finite time and finite resources. Why spend any of that on something a random web dev. can easily implement as a JS library?