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

91–100 of 221 posts

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

#91

Post by radium3d »

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…

Difficult to say without proper debugging tools. Chrome dev tools seems to cause it to not run for me.

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

#93

Post by WhackyIdeas »

Saris wrote: post #84
wg0 wrote: post #60

Reporting from a budget Android Tablet with Firefox, the response times aren't exactly instantaneous but aren't any different than running full LAMP on a reasonable cloud instance or VPS which is surprising to say the least. Also imagine the software layers at play here. Whole PHP Interpreter plus whole thousands of lines from WordPress codebase plus SQLite. Amazing when that's all so much totally useable.

I've always found WordPress performance doesn't change much on lower vs higher end hardware. It seems to be limited by itself.

Absolutely. The other day, I took my slow Wordpress server hosted at Vultr on bare metal (£200/pm) and put it on a server at £500 per month and even after doing all the performance tuning I could with MySQL and PHP I couldn’t notice a difference in speed when I was on the back-end where Cloudflare wasn’t caching it.

I then tested on a lower performance server which costs £80 per month at Vultr and again couldn’t detect any difference when in the back-end.

No matter what performance tuning I done, I couldn’t make it work faster for us. But at least I am on an £80 server instead of a £500 server I guess.

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

#94

Post by EGreg »

graiz wrote: post #29

No need to dunk on wordpress but it has a lot of history and issues. It would be great to have a modern alternative self-hosted solution that doesn't require static site generation or complex hosting.

Ok. Here it is:

https://github.com/Qbix/Platform

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

#95

Post by benatkin »

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…

> in which case what exactly is the other 1.09GB of RAM being used for?

Wrong answers only?

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

#96

Post by btown »

bamfly wrote: post #33
graiz wrote: post #29

No need to dunk on wordpress but it has a lot of history and issues. It would be great to have a modern alternative self-hosted solution that doesn't require static site generation or complex hosting.

Any competitor has a nasty chicken/egg problem to overcome. Wordpress is still hard to avoid because there's a plugin—usually with paid support available—that can do damn near anything. The codebase isn't great, developing against it sucks, and the way it's designed and the official store curated does nothing to prevent some real messes & risks on the database side—but, two days of set-up and $80/m in plugins/themes…

See also Salesforce and Shopify, whose app store/plugin ecosystems give them a network effect in their spaces in much the same way - but equally tie them to antiquated API surfaces due to their commitment to backwards compatibility.

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

#97

Post by andrewaylett »

lolinder wrote: post #78
kodah wrote: post #51

Earlier quoted context omitted.

> Most of the gatekeeping of what is and isn't "coding" is done by novices who don't really know what they're talking about. Beginners tend to want a hard line with "coding" on one side and "not coding" on the other, but that's not a very useful way to model interactions with computers. I disagree. There's a meaningful distinction between what is code and what is formatting because the concerns are quite different. T…

I agree that the distinction you're drawing is valuable, but it's not a distinction between "code" and "not code": both aspects are defined with a language that the computer parses, interprets, and executes on. One happens to be a declarative language that deals with the what and why , and the other an imperative one that deals with the how . > Trying to shoehorn peoples attitudes into discriminatory experience level…

It's not "code" and "not code", it's "software engineering", "programming", and "using a computer".

So many more people program computers than think they're programming. Anything that allows a computer to reproduce what would otherwise be a manual set of steps is programming. Made a bookmark in your browser? That's programming. Excel is definitely programming. And have you ever tried styling a web page using only the browser dev tools? CSS is hardcore programming, and people who claim otherwise are often snobs who find CSS too hard so they call it "not programming" in order to feel better about themselves.

Software Engineering is a whole different ball game. It's not so much what as how and actually the "programming" bit is almost always the easy part. That's why Software Engineers run away when someone asks them to look at "this really useful spreadsheet than $PERSON made" -- chances are that person doesn't think of themselves as a programmer, but that's what they've been doing and they're actually really good at it. But only in isolation, while Software Engineering involves working with whole systems and (more importantly) both the people who use them and the people who work on them.

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

#98

Post by bunga-bunga »

toddmorey wrote: post #14

"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.

Finally some RAM competition to Electron apps!

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

#99

Post by coder543 »

radium3d wrote: post #87
calibas wrote: post #21

Earlier quoted context omitted.

Neat, and here's more info on how they did it: WebAssembly PHP: https://wordpress.github.io/wordpress-playground/architectur... Service Workers: https://wordpress.github.io/wordpress-playground/architectur...

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

The browser task manager may claim that, but actually watching Windows Task Manager, my total memory usage increases by about 300MB when I visit the playground, not 1GB. Maybe a lot of the memory is uncommitted.

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

#100

Post by judah »

Saris wrote: post #84
wg0 wrote: post #60

Reporting from a budget Android Tablet with Firefox, the response times aren't exactly instantaneous but aren't any different than running full LAMP on a reasonable cloud instance or VPS which is surprising to say the least. Also imagine the software layers at play here. Whole PHP Interpreter plus whole thousands of lines from WordPress codebase plus SQLite. Amazing when that's all so much totally useable.

I've always found WordPress performance doesn't change much on lower vs higher end hardware. It seems to be limited by itself.

What's the answer to making WordPress sites faster?

I too have tried better hardware, CDNs, plugins like WP Super Cache, and others means of optimizing. Very little impact. Is the problem PHP?

I'm thinking of trying one of those plugins that convert the WordPress site to static web site. I'd imagine that'd have a big impact, at least for sites that don't need e.g. login, shopping carts, etc.

Post reply on HN