261–270 of 371 posts
1. Viewers
2. Writers/Editors
3. Maintainers
Technology tools are just means to an end.
I am sure there are people from https://www.usds.gov reading this. And I hope they would cherish the great opportunity of a green field to build a secure, robust public service system that are enjoyable to use for all types of users.
Wish them the Best.
Earlier quoted context omitted.
The 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.
Those 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..…
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.
The whitehouse probably needs a fast way to publish. this is why they used wordpress. They are fully cached behind Akamai CDN. So u can hit this website with any load u want. The performance of wordpress is excellent if you dont have many plugins. It is super-easy to design. you can see the results before you publish and You dont need a developer to publish. So if u have a static wordpress website, just add a CDN in…
Even without plugins, WP performance will start to degrade due to how it handles post "meta" data. As the wp_postmeta table grows larger in size, it will generate longer running queries as it tries to query against non-indexed key + values. At a certain point, your only option is to start modifying WP core code and the DB tables for your specific needs...which at that point, the poor software architecture becomes an enormous problem. Granted most small blogs will never see these kinds of issues since they will never reach these inflection points, but they needlessly exist none the less.
Is there a good alternative to WordPress?
Is there a good alternative to WordPress?
Earlier quoted context omitted.
There is nothing wrong with Wordpress and the LAMP stack. It’s fine for many great use cases. It powers, and will continue to power many of the biggest sites in the world. Static sites are a tradeoff, and you’re often dealing with other messes especially with non-technical users.
The problem isn't LAMP, the problem is wordpress. It stores state that should be in files in the database, and state that should be in the database in files, so they are tightly coupled, and you have to snapshot both at the same time. It's also a security nightmare and runs dynamic code on every page load by default, so a fresh wordpress install in its default state will fall over when on HN on Reddit or Slashdot, un…
Earlier quoted context omitted.
> 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 modi…
The 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.
Earlier quoted context omitted.
> 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 modi…
> 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.