Re:SQLite in the browser with WASM/JS - OFFICIAL
by modeless on Friday October 28, 2022 @05:43PM
(#33378315)
The web platform has tons of very high level stuff in it, much higher level than SQLite, and more is being added. Even specifically on the topic of 3D, they're trying to add a <model> tag and standard 3D model file format to HTML right now. It doesn't make sense to reject Web SQL, which is much more foundational, on the grounds of being too high level. Not now, but even less so back when the decision was made in 2010, when the web itself was all higher level and the lower level APIs you mentioned didn't even exist.
Re:SQLite in the browser with WASM/JS - OFFICIAL
by nl on Saturday October 29, 2022 @02:08AM
(#33381434)
> they're trying to add a <model> tag and standard 3D model file format to HTML right now.
To clarify, Apple made a proposal[0] which got no real traction. It has migrated[1] to a Javascript API[2]
[0] https://github.com/WebKit/explainers/tree/main/model
Re:SQLite in the browser with WASM/JS - OFFICIAL
by modeless on Saturday October 29, 2022 @02:29AM
(#33381531)
This is wrong. It moved to the immersive web CG but that doesn't mean it changed form to a JS API. It's just a venue change. The WebXR repo you linked is a different project entirely. The new location for <model> is here: https://immersive-web.github.io/model-element/
Re:SQLite in the browser with WASM/JS - OFFICIAL
by haimez on Friday October 28, 2022 @06:48PM
(#33378944)
All of these APIs are going to be very reliable fingerprinting opportunities, especially in combination. Keep that in mind when you think it’s going to be great for your web browser to also be a full featured application runtime.
Re:SQLite in the browser with WASM/JS - OFFICIAL
by nl on Friday October 28, 2022 @11:19PM
(#33380666)
Don't hold back the one open platform there is (the web) with fingerprinting concerns when its competition (mobile platforms) require an identity to use them.
The enemy of progress is perfect.
Re:SQLite in the browser with WASM/JS - OFFICIAL
by haimez on Saturday October 29, 2022 @12:50AM
(#33381085)
I’m supposing that the problem is that the web browser is the universal platform for all applications. There’s a benefit for information consumption (web pages) being separate from functionality rich and infinitely fingerprintable “native capabilities”
Re:SQLite in the browser with WASM/JS - OFFICIAL
by nl on Saturday October 29, 2022 @02:02AM
(#33381410)
I've been using the web since 1994. It's always been an application platform and anyone who says otherwise is misremembering.
> I’m supposing that the problem is that the web browser is the universal platform for all applications
This is a feature not a problem.
> There’s a benefit for information consumption (web pages) being separate from functionality rich and infinitely fingerprintable “native capabilities”
What exactly is that benefit supposed to be? If you want a read-only publishing platform, put PDFs on a FTP site.
WebGL/GLSL give the developer a low level api to the graphics hardware.
Video decoding apis talk to the hardware video decoding hardware.
OPFS gives developers a low level API to the persistent file system / HDD / SSD.