111–120 of 221 posts
._wrapper_5didy_26 {
padding: 0;
height: 100%;
}
._window_5didy_31 {
max-width: none;
}
._experimental-notice_5didy_9,
._toolbar_5didy_64 {
display: none;
}Earlier quoted context omitted.
It makes complete sense. Php web stack is very light compared to Python/node, so it makes sense it can be embedded in the browser.
Except this is already running on a js environment in the browser (usually v8 if you use chrome, edge or any of their derivatives, the engine behind node). So you are running something to not run the thing you are already running.
Earlier 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.
PHP is fast for a dynamic language (compared to say Ruby/Python and even JS). It has the disadvantage that it gets slow by default the more code you have, because it has a static execution model.
WP is extremely bloated and slow though. You can only make it fast by telling Apache to not execute it and hitting your cache (or with a caching layer in front).
With heavy caching (flushed on data changes), hand written themes and plugins, modern build tools for frontend assets, image optimization etc. You can get get top metrics.
However, that's just frontend. The admin panel is always slow.
If your use-case allows it, you rather build one with something like hugo. Hugo and similar are very easy to use and net you much better results.
My general tip is to not build websites with WP if you have web development skills.
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.
There are many functionally perfect substitutes, unfortunately the WordPress value proposition is actually it's ecosystem of plugins, developers and advocacy of it's users. We've all met the client who wants WP and nothing else. And there are countless times we've rolled a clean new solution out, but the client goes back to WP. I have seen value in hybrid approaches, a custom app written in some other framework for c…
Earlier 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.
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 dete…
Earlier quoted context omitted.
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 dete…
Just come to WP.com and we'll run it super-fast, auto-updated, and secure for $25/mo.
WordPress 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 playground, which is running PHP in WASM, is much snappier than 95% of garden variety websites.
I also think the SPA parts of this (the post/page and site editors are very complex React applications) feel snappier in this demo than they do on my local dev environment. Really shows how good SPAs can be when you cut out server round trips.
Disclaimer: I work for Automattic, and this has been a super cool experiment to watch.
WordPress 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…
Naturally all of these things have limits and quality issues that some percentage of users eventually face. That is in of itself fine.
The problem arises when it is expected of a professional to integrate or build on top of these.
People come to web developers with quality expectations, unique problems and requirements. But the legacy that is WP puts so many stumbling blocks and gotchas in the way of these goals that it's not worth it to put a square peg into a round hole.
(Similar can be said about common CRM and ecommerce platforms and solutions.)