Earlier quoted context omitted.
Didn’t know you owned that domain. How/when did you get it?
It's Matt. Automattic CEO.
I know. Still curious about the 2-letter .com though
WordPress Playground: A WordPress that runs entirely in the browser
121–130 of 221 posts
Re: WordPress Playground: A WordPress that runs entirely in the browser
#122Earlier 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.
First, seconding everything dgb23 said in this thread.
I think if you don't have a need for that dynamic stuff, yes a static site generator is a slam dunk in my humble opinion.
The PHP/Wordpress model where pages are composited dynamically for each pageview was an idea that made sense 20+ years ago. Whereas today, regenerating 1000 (or 10,000) static HTML pages can be done in a few seconds anytime a new blog post is made, giving up-to-date sidebars, homepage and stuff. Other code which needs to be dynamic can usually be fully client-side. And for comments, I don't think almost anyone uses the WP comment feature anymore. It's either off due to spam, or delegated to Disqus or similar. That, combined with the constant stream of WP 0-day exploits, really argues for having your actual WP instance behind your firewall and serving your files from an S3 bucket or plain Nginx (etc).
Re: WordPress Playground: A WordPress that runs entirely in the browser
#123WordPress exposes a huge divide in the HN crowd: - one group recognizes WordPress for what it is: a value-multiplier used by non-coders for websites so they don't have to deal with the coding and can focus on their core competencies - the other group hates WordPress because of the ugly codebase, and meanders off to work on their own perfectly formatted, ultra-scalable code that has no little to no value because it's…
> meanders off to work on their own perfectly formatted, ultra-scalable code
Or stops working on their current, imperfect codebase to start a new project that will be perfect… that’ll show ‘em.
Re: WordPress Playground: A WordPress that runs entirely in the browser
#124The question is — how does your WebAssembly in the browser run a server that can listen for incoming requests and serve the page? I don’t get that part at all.
I think this is the part done with the Service Worker, which intercepts network requests: https://developer.mozilla.org/en-US/docs/Web/API/Service_Wor...
Re: WordPress Playground: A WordPress that runs entirely in the browser
#125Just because you can doesn’t mean you should.
Re: WordPress Playground: A WordPress that runs entirely in the browser
#126Re: WordPress Playground: A WordPress that runs entirely in the browser
#127WordPress was where I got my start, a while ago now. From poking around with PHP files, to building my own things, to Django, and on. It would have been inconceivable back then (mid noughties) that the whole thing could be done client side. The Web has come on a long way. These days I tend to hate WordPress with a passion. Occasionally I will be asked to peek at some technical problem with a WordPress installation an…
We do need to figure out as a community how to deal with that upsell / aggressive plugin problem. I hope we can come up with some norms and standards for what's allowed in our plugin directory that is most customer-centric.
Re: WordPress Playground: A WordPress that runs entirely in the browser
#128Earlier quoted context omitted.
What no-code alternative would you recommend for pro web designers?
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-…
I hope we can make the .org Theme directory so good and Gutenberg + Patterns so usable you don't need to go to Themeforest anymore.
Re: WordPress Playground: A WordPress that runs entirely in the browser
#129WordPress exposes a huge divide in the HN crowd: - one group recognizes WordPress for what it is: a value-multiplier used by non-coders for websites so they don't have to deal with the coding and can focus on their core competencies - the other group hates WordPress because of the ugly codebase, and meanders off to work on their own perfectly formatted, ultra-scalable code that has no little to no value because it's…
This is a reasonable position and with the utility sites I build for, say, bands I play with I totally agree. I toss some shit on commodity hosting and hope the band breaks up before the gcal integration breaks. -=-=-= However. I will now take this opportunity to vent a bit, though it has little to do with your imminently reasonable post. Mostly because I am procrastinating on porting a 3rd-party SSO system from a ve…
I'm happy to pitch in and help migrate those university sites, we can get them on a WordPress stack that's much more stable and forward-compatible.
Re: WordPress Playground: A WordPress that runs entirely in the browser
#130I 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.