Nice! See also https://wordpress.wasmlabs.dev/
On linux chromium 7.5GB of memory and 100% of one cpu.
Got SIGILL.
WordPress WASM
41–50 of 69 posts
Re: WordPress WASM
#42WASM 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.
And thanks to Chrome one severe bug will effect all around the globe. Monocultures are susceptible to pests and diseases
fixing a problem, by creating a new problem(s). that's what we do here.
Re: WordPress WASM
#43I 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…
This is certainly a cool idea, but I don't understand a few things about how reality would work with an async reconciliation process on the database layer:
1.) How would the auto-incremented ID fields be merged in such a system?
2.) How are unique constraint violations handled?
Re: WordPress WASM
#44For those wondering about the "why", this post details the motivation: https://make.wordpress.org/core/2022/09/23/client-side-webas... Basically for learning/interactive tutorials, trying out something quickly in different PHP versions (which is cumbersome right now), secure and easy demos for themes and plugins.
Pretty amazing to get all of PHP working in WASM. Next maybe we can get full MySQL, too (like the Crunchy Postgres port [0] [1]).
Would also love to see it for Java, Go, Perl, Sed, and Awk :)
What if Intelli-J could run in the browser? Yes please.
I bet some of these even already exist. What a time to be alive, 15 years ago I'd never have guessed Javascript could evolve into this!
[0] https://www.crunchydata.com/blog/crazy-idea-to-postgres-in-t...
[1] https://news.ycombinator.com/item?id=32498435 (August 22, 2022; 814 points, 172 comments)
^ n.b. Submitted by @samwillis
Re: WordPress WASM
#45I 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…
This is certainly a cool idea, but I don't understand a few things about how reality would work with an async reconciliation process on the database layer: 1.) How would the auto-incremented ID fields be merged in such a system? 2.) How are unique constraint violations handled?
Don't use auto-increment. Use a ULID or some other algorithm driven PK
Re: WordPress WASM
#46WASM has in a way picked up and succeeded where Java applets left off.
Re: WordPress WASM
#47For those wondering about the "why", this post details the motivation: https://make.wordpress.org/core/2022/09/23/client-side-webas... Basically for learning/interactive tutorials, trying out something quickly in different PHP versions (which is cumbersome right now), secure and easy demos for themes and plugins.
No post body was provided.
Re: WordPress WASM
#48This seems like a "can't see the forest through the trees" project. If you don't want to run a server, there's no need for WordPress in the first place - just use a static site generator, or a SPA that uses static content as the backend. Have done a lot of WordPress development, and I love it, but it doesn't seem like it fits this use case better than other options.
Re: WordPress WASM
#49Re: WordPress WASM
#50This seems like a "can't see the forest through the trees" project. If you don't want to run a server, there's no need for WordPress in the first place - just use a static site generator, or a SPA that uses static content as the backend. Have done a lot of WordPress development, and I love it, but it doesn't seem like it fits this use case better than other options.
Static site generators require a headless CMS and all the headless CMS I tried are much harder to use and way less flexible then WordPress.