Ooops! I suppose it does not work in private browsing mode.
WordPress Playground: A WordPress that runs entirely in the browser
101–110 of 221 posts
Re: WordPress Playground: A WordPress that runs entirely in the browser
#102Earlier quoted context omitted.
What no-code alternative would you recommend for pro web designers?
You can't design anything in WordPress without code. Unless you count installing a theme as "design". If you're a pro web designer you should know CSS. Then there's some good alternatives.
I might have misinterpreted your comment, but there are plenty of site builders for WordPress (WYSIWYG-ish editors). Granted, you can only do so much without knowing CSS.
Re: WordPress Playground: A WordPress that runs entirely in the browser
#103Earlier 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 like 1997 I was doing some work with a 5x86-133 with 24mb ram and a 2gb disk, running NT 3.51, MS SQL server, IIS and Visual Studio 4. IIRC, the servers usually ran in less than 500kb committed each.
Re: WordPress Playground: A WordPress that runs entirely in the browser
#104Earlier quoted context omitted.
> 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?
Caching alternate data streams
Dr. Watson
McAfee antivirus
Re: WordPress Playground: A WordPress that runs entirely in the browser
#105This playground, which is running PHP in WASM, is much snappier than 95% of garden variety websites.
[deleted]
Re: WordPress Playground: A WordPress that runs entirely in the browser
#106Earlier 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…
> 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
Only being half-facetious here: if the old stack was so great, why aren't you still using it? I know someone who swore by ColdFusion, but won't use BlueDragon or Lucee because the world has moved on from CFML; templated HTML-generation on the server is no longer the only game in town
Re: WordPress Playground: A WordPress that runs entirely in the browser
#107Earlier quoted context omitted.
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.
The problem is the ecosystem. You can get response times for the main page down pretty low (especially with caching plugins) and the time to serve static assets is the same for Wordpress or a static site. Most likely if your site feels slow, the culprit is your theme and one or more plugins on your site. You can usually track down problem plugin(s) using PageSpeed Insights since their frontend assets are served from the plugin folders.
Re: WordPress Playground: A WordPress that runs entirely in the browser
#108No 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.
Wordpress is the success it is today because over the years, while other CMS kept breaking API, Wordpress remained mostly stable, allowing the development of a large ecosystem of plugins.
Another thing is that Wordpress PHP API uses very little OOP. It's mostly functions + arrays. So people who know very basic programming could write their own plugins, themes and co.
Re: WordPress Playground: A WordPress that runs entirely in the browser
#109Its cool and I get it, but how is this useful other than good marketing? If an app's code is run on a device, any rooted device could just modify its memory and do whatever it wants. Just ask a game developer about the infinite anti-cheating war that they deal with.
> ...any rooted device could just modify its memory and do whatever it wants
Like what? Change a heading? Or, create a blog post that only exists on this device?
Re: WordPress Playground: A WordPress that runs entirely in the browser
#110Can 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?