111–120 of 371 posts
Redacted.... forgot that HN has zero sense of humor.
This kind of elitist rhetoric is really not constructive. Implying somehow that WordPress developers aren't "talented" because they don't use your tech stack is incredibly ignorant.
Earlier quoted context omitted.
> A bad idea, IMO. It's still going through the PHP server and all of the routing/plugin/DB code within WP. Much better to use Varnish (and its ilk) and avoid overloading the PHP service. I'm not a big WP fan, but this statement is false in most cases. Page caching in WordPress is usually (always?) serving up the pre-rendered HTML direct from disk (or CDN) without hitting PHP. Pagely (the post we're discussing) even…
> Page caching in WordPress is usually (always?) serving up the pre-rendered HTML direct from disk I'd be very curious how a WP plugin is managing this. Third party hosting building in caching, normal in-line caches (like Varnish), nginx/apache caching, sure - I get those, and they behave how you say. But a WP plugin? I'm curious how that would bypass PHP & WP entirely.
I feel improving the security architecture of plugin integration could go a long way. Although using lesser plugins, only from trusted developers, keeping them updated, using other security plugins(Firewall, 2FA etc.) and regular backups can help keep WP instance safe to some extent; There's absolutely no excuse or explanation for random database errors with WP and that was the final nail in the coffin for me.
I started building my own CMS using Go for complex websites and for simple websites static web pages using Hugo with markdown does the job.
Earlier quoted context omitted.
From an operations perspective, gatsby and next.js are much simpler though. You are just deploying static content behind a webserver or even something like s3. Horizontal scaling is almost trivial. With wordpress though, you have to worry about a database as well, scaling is more complicated, you need to run php on your webservers (which has security implications), updates that include schema updates frequently requi…
Wait, what non-trivial site doesn’t require a database?
> Political affiliations aside, I think we can all breathe a bit easier today knowing they didn’t choose Drupal. Strongly disagree. Drupal is a great CMS and there's a reason the government uses it so extensively.
I'd still choose it over WordPress any day. But the days when I'd recommend either of them (or indeed anything in PHP) are long gone. Your best bet now is probably a static site generator such as Hugo. If you insist on staying in database-driven CMS land, at least go with Django or Rails.
I was curious after seeing the accessibility statement what the previous administration's had. https://www.whitehouse.gov/accessibility/ https://obamawhitehouse.archives.gov/accessibility https://georgewbush-whitehouse.archives.gov/accessibility.ht... https://trumpwhitehouse.archives.gov/accessibility With that last one not being surprising at all.
Earlier quoted context omitted.
WordPress is not without its design flaws, some of which make sense from the point of view of helping non-techies run their own sites (such as making updates easy.) But as someone who has built 100s of sites with WordPress I feel the need to defend it on a few points here: > You have to let it modify its install. Security-fucking-nightmare. You don't have to do this, you can set up sane permissions and use the wp cli…
> You don't have to do this, you can set up sane permissions and use the wp cli[0] tool to install updates manually. I prefer to version sites with git and install updates locally, then git pull down on to the live server. Curious as to how you manage WP with git, particularly around when new files are added by core/plugin updates, which I've always found a bit of a hassle to deal with?
Earlier quoted context omitted.
This kind of elitist rhetoric is really not constructive. Implying somehow that WordPress developers aren't "talented" because they don't use your tech stack is incredibly ignorant.
Static sites aren't really a "stack", but I do agree that static generation isn't really appropriate for a website like whitehouse.gov
So if u have a static wordpress website, just add a CDN in front (not using a plugin like many do, but by editing your DNS)
I hope we again see the value of using systems like Wordpress for it’s simplicity in getting a blog/website setup and easily modify content. Lately most of the modern marketing websites I see is built using gatsby and next.js. Having been talking to different content/marketing teams, they hate it so much because of the complexity it brings. Editing content? Sign in to this headless CRM app, want a form? Go sign in to…
From an operations perspective, gatsby and next.js are much simpler though. You are just deploying static content behind a webserver or even something like s3. Horizontal scaling is almost trivial. With wordpress though, you have to worry about a database as well, scaling is more complicated, you need to run php on your webservers (which has security implications), updates that include schema updates frequently requi…