Live data from Hacker News

WordPress Playground: A WordPress that runs entirely in the browser

developer.wordpress.org

151–160 of 221 posts

Re: WordPress Playground: A WordPress that runs entirely in the browser

#151

RIP static site generators. Just run this in your browser and export a static site. No more complicated setups. No more running ruby in docker or fighting hugo templates. Install the themes and plugins and go nuts! /hottake

Tools for that purpose already existed, e.g. WP2Static.

Sure but you had to install wordpress on your PC: hard or server: easier but cost $ on top of the static hosting bill

Re: WordPress Playground: A WordPress that runs entirely in the browser

#152
post #24

Genuinely curious: does this mean you can run WordPress as a cloudflare worker (ignoring database for now)? https://developers.cloudflare.com/workers/runtime-apis/webas...

The team behind this tried to deploy to Cloudflare but hit memory constraints with Workers due to the 128MB limit there:

https://github.com/WordPress/wordpress-playground/issues/69

There’s likely more work that could be done to make this viable, though (or Cloudflare could raise limits).

Re: WordPress Playground: A WordPress that runs entirely in the browser

#153
post #24

Genuinely curious: does this mean you can run WordPress as a cloudflare worker (ignoring database for now)? https://developers.cloudflare.com/workers/runtime-apis/webas...

The team behind this tried to deploy to Cloudflare but hit memory constraints with Workers due to the 128MB limit there: https://github.com/WordPress/wordpress-playground/issues/69 There’s likely more work that could be done to make this viable, though (or Cloudflare could raise limits).

So what's the min limit required to make it run?

Re: WordPress Playground: A WordPress that runs entirely in the browser

#154
I use WP all the time for a variety of nearly static sites that I can let someone else non-technical continue to add content. It works great for this purpose. There is nothing close to WP for this purpose.

It does need careful curating of plugins that one uses, set up suitable cloudflare frontends and preventing users from doing something seemingly simple but dangerous.

I get the feeling that a good chunk of the hate comes from people who tried it many years ago; or had needs which don't get met by WP; or received it as a legacy.

Re: WordPress Playground: A WordPress that runs entirely in the browser

#155

I tried to make a big deal about this in my State of the Word keynote in December 2022: https://wordpress.tv/2023/01/04/matt-mullenweg-state-of-the-... It kind of blew my mind as an engineer to see it work, and know all the layers that had to interact for that to happen. It's fun to see it blowing up on HN 6 months later! :) Thank you to everyone for checking it out.

Nice talk! For anyone curious, 48:33 is the timestamp where Wordpress Playground is introduced

Re: WordPress Playground: A WordPress that runs entirely in the browser

#156
post #110

Can we just throw wordpress in the trash instead already? It sucks at everything. It's not a good CMS, its plugins are awful, PHP is a dumpster fire, every web developer hates it, etc. This is also pointless as a tech demo.

That must explain why WordPress' market share has been trending downwards for the last 20 years, right?

Yes! Ignorance absolutely explains its "market share". There's no reason for anyone to be running this trash in 2023. I'm surprised Shopify hasn't completely wiped out Wordpress for ecommerce yet. For all other kinds of websites, they don't even need a CMS. Blogs are dead so it's all niche sites that demand custom web dev by now.

Re: WordPress Playground: A WordPress that runs entirely in the browser

#157
post #153

Earlier quoted context omitted.

The team behind this tried to deploy to Cloudflare but hit memory constraints with Workers due to the 128MB limit there: https://github.com/WordPress/wordpress-playground/issues/69 There’s likely more work that could be done to make this viable, though (or Cloudflare could raise limits).

So what's the min limit required to make it run?

They estimate ~155MB just to get PHP running in Workers. It will be more to load WordPress. And there is extra work to get it running with Cloudflare D1. Plus everything else that likely won’t work by default there (e.g. image uploads).

Re: WordPress Playground: A WordPress that runs entirely in the browser

#158

Earlier quoted context omitted.

I know. Still curious about the 2-letter .com though

Domains are my vice. Also have w.org. Ma.tt. I would rather have a cool IP address (like Cloudflare's) or domain than a fancy car or boat.

The link in your profile doesnt work - http://www.justin.tv/startupschool/b/298808177

Re: WordPress Playground: A WordPress that runs entirely in the browser

#159

"Whether you want to build a note-taking application for mobile devices, an automated testing environment, or demo a live WooCommerce store on your site – Playground will support you." The last two make a ton of sense, but the idea of building a mobile app that's powered by Wordpress running PHP in webassembly in the browser is wrecking my brain.

We need an LLM layer for this to truly be web-scale.

Re: WordPress Playground: A WordPress that runs entirely in the browser

#160

I use WP all the time for a variety of nearly static sites that I can let someone else non-technical continue to add content. It works great for this purpose. There is nothing close to WP for this purpose. It does need careful curating of plugins that one uses, set up suitable cloudflare frontends and preventing users from doing something seemingly simple but dangerous. I get the feeling that a good chunk of the hate…

A combination of the second, third and a client who insisted on using it for a project where a headless CMS + custom code would have worked a lot better did the trick for me.

Still not really WP's fault, but it doesn't change the fact that I recoil a bit in horror when it's mentioned.

Post reply on HN