What does it even mean to run PHP in the browser... Is this supposed to be some sort of replacement for server-side PHP?
First thing that came to mind is that I could load this up on a static host, saving content in a local SQLite (or even in SQLite in S3), make changes and then export the results to S3 as static HTML files. All without ever running any PHP/SQL host. One could technically upload this to GitHub Pages. Endless possibilities!
WordPress WASM
21–30 of 69 posts
Re: WordPress WASM
#22WASM may offer the most secure-by-default installations of Wordpress to ever exist. This is seriously impressive -- I think we're getting a glimpse of a world where people can really run server side apps on their computers easily. Add an app store and the web will have finished becoming the platform that everyone has been suspecting it is.
So from user perspective, they still have to run it like they would run local web server but more secure? It's improvement security wise, though it's still hustle for app distribution right?
> Add an app store and the web will have finished becoming the platform that everyone has been suspecting it is.
Basically what we need now is a user-side "app store" that downloads apps packaged as WASM and runs them!
Honestly this setup could probably work today, use something like Tauri[0] to build a simple app-store like experience. When someone installs an app, this thing downloads the WASM, and runs it with the necessary linked modules (local file access, network).
Then, you can spin up a new window that is the new application, and keep it running/do whatever else users would expect. I mean you could even launch the apps standalone/separate processes as well so that people can close the original one (or put it to tray, whatever).
This could easily be like snap/flatpak but even better in some ways. Browser technology is almost assured to always be moving forward and getting more powerful/impressive because of the large interests involved.
Re: WordPress WASM
#23If it worked fully of course, which it currently doesn't.
Re: WordPress WASM
#24Re: WordPress WASM
#25Earlier quoted context omitted.
So from user perspective, they still have to run it like they would run local web server but more secure? It's improvement security wise, though it's still hustle for app distribution right?
Yup, that's why I put in that last part: > Add an app store and the web will have finished becoming the platform that everyone has been suspecting it is. Basically what we need now is a user-side "app store" that downloads apps packaged as WASM and runs them! Honestly this setup could probably work today, use something like Tauri[0] to build a simple app-store like experience. When someone installs an app, this thing…
Re: WordPress WASM
#26Re: WordPress WASM
#27In this way the server could serve a cached page on first request, then the wasm file would be downloaded. From then the whole rendering could be client side, while still fetching data from the remote DB. This could significantly speed up things for users.
Re: WordPress WASM
#28It's probably the most secure way to deploy Wordpress soon.
Re: WordPress WASM
#29Re: WordPress WASM
#30I think this is a really compelling pattern for converting traditional server rendered apps to be offline enabled (or choosing to build new ones this way). I have seen similar examples using Python. Initially these are more of a “backed data” type app, with no offline public writes. [0] The next step is to have local/offline SQLite to server syncing, enabling writes while offline that are synced back to the server on…