6 ms·
>Simplicity? Perhaps in its use, but not the code. Nobody but other devs cares about the simplicity of the code if the code works. >The code and hosting requi
by coldtea 6y ago
>Simplicity? Perhaps in its use, but not the code.
Nobody but other devs cares about the simplicity of the code if the code works.
>The code and hosting requirements are, frankly, Frankenstein's monster levels of frightening.
Huh? Wordpress/PHP hosting requirements are the easiest to meet in the industry. Not to mention the most widely available...
>~~You have to~~ WP expect you to install it such that it can modify its install folders - all of them. Security-fucking-nightmare.
Yeah, so? It's self-updatable. Use a dedicated user/group.
>It falls apart under any kind of load, both because of unoptimized DB queries, and because of PHP.
Absolutely not "because of PHP". If anything PHP is faster than both Ruby and Python, two other common choices.
>You have to put a cache in front of it to be able to handle getting on HN, let alone Reddit.*
That's the case with most CMS, PHP or not.
>Arbitrary plugin installation, in a non-sandboxed environment (see prior point about an application-writable install).
It only happens if you chose to do it. Plugins don't magically install by themselves.
So it's not much different than any environment where you can download a jar, a python package, a ruby gem, etc and have them add functionality into the CMS.
>Need more be said?
More, no. Better, yes.
- captn3m0 6y agoWordpress is also the only CMS that offers multisite hosting - single codebase, single webserver, one docker container - for running multiple sites with different configuration. You wanna run 2 blogs on Ghost - run 2 instances, same for _everything but Wordpress_.
- thg 6y agoTypo3 can do that too.
- Kimitri 6y agoWell, Drupal has multisite capability, too. I don't think using multisite is actually that good an idea. Having two separate websites be dependent on the same codebase is very prone to cause serious life cycle problems. I'd advice against using multisite on WP or Drupal.
- 42droids 6y agoWe have been doing this successfully for many years, no problems. Some multi site installs have up to 300 sites running on them. You have to know when to use the available technology.
- DigitalSea 6y agoSpot on. I am currently working on a project that has over 25,000 multisites running in WordPress Multisite. The amazing thing besides the sheer number is WordPress has not been a problem, throw it on AWS and the scaling issues are solved. People who proclaim that WordPress can't scale have never built anything scalable with it.
- photomatt 6y agoAwesome example, thank you for sharing!
- interfixus 6y agoTextpattern does that easily enough. You can even run your admin stuff on a different domain if you so desire.
- newsbinator 6y ago> Nobody but other devs cares about the simplicity of the code if the code works. They care when you start quoting a week for a simple addition that should take an hour, because every time you have to wade into a mess, in which one wrong semicolon in functions.php brings down the entire website. Of course you test and you test, but you're surrounded by landmines at all times.
- tomduncalf 6y ago> They care when you start quoting a week for a simple addition that should take an hour Exactly, this is the key point. If it’s a website that literally will never change then fine (edit: what I mean here is if you are confident WP can meet your needs without resorting to hacks, and can meet your future needs - in my experience, it’s when more functionality gets added on by random developers that things get messy, true of development in general though!). I guess using headless WP might help? The clients I’ve worked with who’ve had WP sites in the past have made a point of saying they definitely don’t want WP again (due to security nightmares, usability etc) so honestly haven’t investigated it too deeply recently.
- iamacyborg 6y ago> in which one wrong semicolon in functions.php brings down the entire website. Don’t immediately deploy code into prod until you’ve tested it?
- YetAnotherNick 6y agoHow do you test wordpress without deploying it? \s
- bartread 6y agoWe do it with a secondary copy of our website. Honestly though, there's a lot of talk about changes here without much talk of the most obvious class of changes that Wordpress is designed to support: adding content to your website or blog. For all its faults it does make that very easy, and it's designed with the intent that you will do so by working directly on the live site (you can obviously preview and review content before making it live). Changing layout and templates is trickier, likewise creating a new page layout, and that's where a staging or development site comes in handy.
- eecc 6y agoWell it’s a security shitshow and a fav for hackers looking for an easy exploit vector: just compromise it once and voila! All website consumers are at risk. Just a shame there’s no liability for negligently causing users to get infected.
- laumars 6y agoThe NFS requirement for multiple Wordpress hosts are an instant deal breaker for me when discussing CMS on the cloud. Wordpress made sense when the web was a collection of independent servers. However in today’s cloud-orientated hosting landscape there are a thousand better ways to provide said content. Both at the beginner level and at the enterprise.
- jspash 6y agoThose independent servers haven’t gone away just because there are new toys in the box. They are still fast, cheap and ubiquitous. I’m no fan of PHP or Wordpress by any stretch. But I agree with the pragmatic choice in this case. It will probably only need one dev to maintain the site. But even that would be overkill. You just never want a bus factor of 1. Especially for such a high profile site. But I’m digressing... But cloud vs VPS aside, I do wonder is they are self hosting due to security reasons. Imagine a bad actor hacking into the WP installation! It does have a bad security record.
- laumars 6y agoSorry, by “independent servers” I meant self hosting / on prem. And while that hasn’t gone away entirely it has diminished massively as companies deprecate on prem hardware as hardware ages and replaces those resources with cloud services. Stuff like NFS made sense for on prem but it’s a terrible solution for building services on AWS (for example). Security wise, any popular CMS will be a security nightmare. It’s not even a PHP thing. In an ideal world you’d stick your CMS behind a WAF and put some additional policies around your admin APIs (if at all possible). Wordpress, for all of its warts, actually made those parts easy to do.
- snowwrestler 6y ago> Security wise, any popular CMS will be a security nightmare. I disagree, and I think it comes from a different understanding of what web security is. Popular CMS software benefits from millions of people hammering on installations. If the community constructs a sane process for handling vulnerability reports (and WP has), then the average user of that software benefits from a robust continuous testing regime that they could never afford themselves. Testing and patching is an extremely important component of web application security in the long run, and also very expensive to do well. Most custom CMS projects do not bother to do it at all, and yet fool themselves into thinking they are secure because they wrote their own code. No one can write secure software on the first try. The most well-funded and well-regarded software companies in the world spend tremendous effort on coding practices and testing, and still ship vulnerabilities. Continuous testing and patching is always required. If your website is the only one running your CMS software, your first hint of a vulnerability may be when it gets exploited in production.
- belorn 6y agoIf people avoid installing plugins and custom themes, and absolutely do not change the theme so that automatic updates have to be turned off, and they also install automatic updates, then its pretty fine. As someone who works professionally at a hosting company, no one does this. The history of Wordpress security has followed window XP with users who downloads random files from the internet and click cancel every time something want to update. Every hosting company that I know has to implement firewall rules to address WordPress security, just like the old days of windows. The default configuration is also not fine. At minimum you need to disable rpc calls to the login, as the password attacks trigger a lot work that eats resources and processes. RPC is on per default in order to make the WordPress mobile app work.