Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

WordPress Playground: A WordPress that runs entirely in the browser

developer.wordpress.org

Post reply on HN
Print view View original

211–220 of 221 posts

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

#211

Post by rapnie »

EGreg wrote: post #207
rapnie wrote: post #168

Earlier quoted context omitted.

Oh no. Still the mouse movement animation on the website? It made me not read further down the page.

I am very sure the Github page I linked to doesn’t have any mouse animations. It has a README right on the page, with all the info. It also lets you clone the code and try it out, watch videos and much more. Did you purposely seek out a different page, see a mouse animation, and then announce to everyone that you did not read further down THAT page because you were distracted by an animation? It seems like a petty th…

Sorry, not my intention. I did give feedback on that animation on main project website before (where I always look in addition to a README). Project is nice, animation is awful. My feedback stands: better to remove it.

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

#212

Post by Vindl »

sogen wrote: post #203
photomatt wrote: post #175

Earlier quoted context omitted.

On the business plan (25/mo) you can run any plugin or theme, or custom code. You also have full SSH/SFTP and wp-cli access.

Can it run custom plugins?

Yes. You can deploy your custom plugins and themes.

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

#214

Post by mattbillenstein »

photomatt wrote: post #177
mattbillenstein wrote: post #166

Earlier quoted context omitted.

I worked on a Strattic conversion some time back - they basically scrape all your pages and serve them statically, but you do have to do some things to support search, forms, etc and you'll end up pruning plugins that don't work well with it. But, serving static pages is very very fast afterwards.

Bet on Moore's Law and go fully dynamic.

Yes, but practically speaking, waiting 20 years isn't an option. Moore's Law has stopped delivering rapid single-threaded performance gains and not everything is trivially parallelable.

The fastest single-threaded cpus today are only 2x faster than the fastest single-threaded cpus of a decade ago...

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

#215

Post by account42 »

photomatt wrote: post #177
mattbillenstein wrote: post #166

Earlier quoted context omitted.

I worked on a Strattic conversion some time back - they basically scrape all your pages and serve them statically, but you do have to do some things to support search, forms, etc and you'll end up pruning plugins that don't work well with it. But, serving static pages is very very fast afterwards.

Bet on Moore's Law and go fully dynamic.

I'll bet on future WP updates eating whatever perf improvements new hardware will give. Besides, Moore's Law is about the number of transistors. Speed - and especially single threaded speed which is what matters for PHP sites - is not going up nearly as fast anymore.

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

#216

Post by imilk »

pentagrama wrote: post #144
imilk wrote: post #40

Earlier quoted context omitted.

Wordpress is still great for downloading a theme from Themeforest to get brochure style sites (restaurant, simple small business, etc) up and running pretty fast. It is not great (possibly horrendous) for revisiting a few years later when all the plugins/theme/core needs to be updated and a bunch of different people have added custom JS/CSS all over in random places. It's hard to reconcile "pro web designer" with no-…

In my experience, I bought some pro/high sellers/high rated themes on Theme Forest for 3 sites, but all of them come with a bunch of pre-installed plugins, and was a mess. Specially two who have a mandatory plugin to edit pages, called WPBakery, damn I hated it, is awful, the native WP editor is miles away (Gutenberg), but the design will brake if you use Gutenberg. Also, this and other plugins do not auto-update aut…

Yeah some themes are way better than others, that's for sure. This is one of the cleanest and most flexible that I've used on dozens of sites, getting them up and running with a branded look in 2-3 hours:

https://themeforest.net/item/salient-responsive-multipurpose...

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

#217

Post by pentagrama »

imilk wrote: post #216
pentagrama wrote: post #144

Earlier quoted context omitted.

In my experience, I bought some pro/high sellers/high rated themes on Theme Forest for 3 sites, but all of them come with a bunch of pre-installed plugins, and was a mess. Specially two who have a mandatory plugin to edit pages, called WPBakery, damn I hated it, is awful, the native WP editor is miles away (Gutenberg), but the design will brake if you use Gutenberg. Also, this and other plugins do not auto-update aut…

Yeah some themes are way better than others, that's for sure. This is one of the cleanest and most flexible that I've used on dozens of sites, getting them up and running with a branded look in 2-3 hours: https://themeforest.net/item/salient-responsive-multipurpose...

The templates on this theme looks really nice and modern, will check it out, but it uses the native WordPress editor or a third party plugin? Also, the pre-installed plugins will update automatically?

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

#219

Post by dmsnell »

DaiPlusPlus wrote: post #88
radium3d wrote: post #87

Earlier quoted context omitted.

Interesting, seems the dedicated worker in chrome task manager is utilizing 1,135,948k of memory

> 1,135,948k of memory That's 1.1GB. That's horrifying because, theoretically, it should be a tiny, tiny fraction of that: on bare-metal we can run PHP + MySQL (let alone SQLite) + Apache within a few dozen MB of RAM. (Historical personal anecdote: my first-ever dev-server machine I built before high-school ran Windows Server 2003, IIS, SQL Server, and Adobe Photoshop 7.0 (in a Terminal Services session) concurrently…

I'm not entirely sure on this, but I believe that what we're seeing is the WASM runtime allocating memory for its potential needs, but not totally using it all.

The entire filesystem, all the executables, all uploaded files, and all database data lives in memory in the virtual filesystem. I think we could trim down the default allocation but it might actually be meaningless anyway; that GB won't steal real RAM unless it fills up inside the environment.

Someone can probably check me on this, but if my memory serves me right this is what's going on.

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

#220

Post by dmsnell »

dboreham wrote: post #209
lioeters wrote: post #205

Earlier quoted context omitted.

There is partial support for persistence, for browsers that have origin private file system (OPFS) implemented. > OPFS is only supported in Chrome-based browsers at the moment like Edge, Android browser. Safari and Firefox users won't be able to benefit from this feature yet Persistent Playground: Sync between MEMFS and OPFS - https://github.com/WordPress/wordpress-playground/pull/546

Very interesting, but I don't think sync from MEMFS to OPFS will work for my use case :( Is there a reason why using OPFS directly from SQLite doesn't work?

The Playground stores more than the SQLite database in OPFS. This includes things like installed plugins and file uploads and other artifacts brought in during boot. If there's enough interest and time I could imagine support being added to separate these, but for now it's easiest to have a single load and store mechanism for everything.

There's a third option supported only in Chrome at the moment which loads a directory from your computer's filesystem, bypassing even OPFS.

> using OPFS directly from SQLite doesn't work?

not entirely following your question. any way you could reword and explain what you were hoping to accomplish?

Post reply on HN