3 ms·
>You, the dev. As per the parent comment, it's not exposed to the javascript running on the page, which is arguably the "dev" in this case. >Not you the clien
by gruez 5y ago
>You, the dev.
As per the parent comment, it's not exposed to the javascript running on the page, which is arguably the "dev" in this case.
>Not you the client, hence the user.
I fail to see how it being exposed to the javascript running on the page or not makes a meaningful difference to the user. Are we expecting the average user to interact with the page via the developer console or something?
>and we all have seen where it leads to.
The proposal doesn't have any DRM element at all. At worse you can just inspect network traffic to download the model file to disk and open it in whatever app you want.
- BiteCode_dev 5y ago> I fail to see how it being exposed to the javascript running on the page or not makes a meaningful difference to the user. Are we expecting the average user to interact with the page via the developer console or something? No, but I'm expecting the average user to be able to enjoy an open ecosystem. Such as bookmarklet, addons, client side widgets, electron apps, WASM plugins, and all the wonderful things we can't yet think of now. Instead, we will have one more walled garden. And just like that, piece by piece, the next step in the IT revolution will be more and more close. Because that's the plan, that's what they want. Something the computer runs, but has no control over.
- gruez 5y ago>No, but I'm expecting the average user to be able to enjoy an open ecosystem. Such as bookmarklet, addons, client side widgets, electron apps, WASM plugins, and all the wonderful things we can't yet think of now. But there's still webgl and <canvas>. I'm failing to see what type of use cases we're missing out on here, because javascript access is missing.
- deleted 5y ago[deleted]