I’ve been a WordPress dev since 3.0. It is a tool. And a very good one. Its market share dominance it not because it is proprietary (it is not) or because of vendor lock in (there is none). It is because it works very well, it is lightweight, it runs pretty much on any host, and is friendly to devs and end users. Part of being a good dev is knowing which tool to use (and when to not use a tool) and how to get the mos…
The complicated futility of WordPress
181–190 of 241 posts
Re: The complicated futility of WordPress
#182Earlier quoted context omitted.
Do they even offer VPS storage in units smaller than a GB these days? No one cares about a 20MB binary.
For what it's worth, I'm running the absolute cheapest DigitalOcean droplet money can buy ($5/mo) and that comes with 25GB of NVME storage as standard.
I don't think that it's very economical to provide smaller instances than that for most cloud hosts out there.
Re: The complicated futility of WordPress
#183My blog has been on Wordpress since about 2007. It works, and I appreciate that it’s free but I’ve always hated working with it. If someone made a node based equivalent (so I can at least use a modern templating language) that supported comments I would be all over it. The commenting system is the only real reason I stay. There’s nothing else I can find that doesn’t necessitate stitching multiple services together ju…
Re: The complicated futility of WordPress
#184Earlier quoted context omitted.
Third-party plugins are subject to WordPress's security model and implementation. Automattic could create a PluginV2 system with tightened security and new requirements for plugin developers, then put a plan in place to deprecate and remove support for v1.
I think it's probably too late to save wordpress. Squarespace and such are just better products for the average company. It would require a fundamental redesign of wordpress to solve its issues and at that point it just becomes a clone of the existing products.
> WordPress is used by 65.3% of all the websites whose content management system we know. This is 43.3% of all websites. [1]
And these numbers have been growing for years. In other words, WordPress is and will be widely used for a long time. So I’m not sure WordPress really needs saving. :p The number of OSS contributors has also been growing. So the project itself hasn’t been stagnating either.
Disclaimer: I’ve been a WordPress contributor and work for Automattic.
Re: The complicated futility of WordPress
#185Earlier quoted context omitted.
It's funny you invoke PowerPoint - MS FrontPage was exactly this tool and it worked reasonably well, as did iWeb. Publishing WYSIWYG websites from the desktop was given up in the 00s, and now we have Squarespace and Facebook Pages.
I was there. It was horrible. FrontPage output was an unholy mess and god help you if you ever needed to dive in that codebase by hand. Current solutions are far from perfect but I never want to go back to that.
Re: The complicated futility of WordPress
#186I feel like this is an unnecessary and inflammatory swipe, typical of coder-bro culture. Both Drupal and Wordpress are open source tools that have survived for years, are built on tested and long-lasting languages, and serve the people who both build and use them.
Everyone is always crying about how nothing ever stays the same, and and the same time, how the-next-new-thing-ism is ruining the web. And then there is this comment thread with every other response trying to push some ostensibly better and easier thing that stands no chance of surviving more than a couple of years, because CMSs need communities to keep them alive.
I am a proud member of the Drupal community. I struggle with it sometimes, but it is still amazing at how much you can accomplish with core and contrib modules. And don't forget, some organizations need a giant, clunky CMS. We're not all building websites for cutting edge, VC-backed, brochure-based unicorns. My clients need a framework that has legs to stand on for the next decade to come.
Re: The complicated futility of WordPress
#187> Sites that have been painstakingly, designed and built, reviewed and refined to the last detail every step of the way with stakeholders on the client side, optimising UX, legibility, performance and upholding the client’s brand can now be squelched in an instant by someone 3 months into their job who prefers yellow.
Completely agree. Back when I was building w/ WordPress, ACF was the best choice for building layouts because you could provide only as much flexibility as you wanted the client to have. You could give them lots of power to easily update their content but constrain their ability to ruin the design. I gave a short talk at a WordCamp about this exact benefit of ACF over page builders (at the time).
Re: The complicated futility of WordPress
#188Earlier quoted context omitted.
I love WordPress. It is kind of a universal tool: you can make simple web sites, you can use it to build complex systems. It is always better if you have developers that know what they are doing. WP development is not installing dozens od plugins to achieve some effect on your web. I guess that WP wants to become "one to rule them all". This means that they strive for even bigger adoption rate among users. FSE is the…
> It is kind of a universal tool: you can make simple web sites, you can use it to build complex systems. It is always better if you have developers that know what they are doing. Here's a question: suppose that you want to use WordPress as a starting point for a CRUD app with some basic permission controls, the ability to dynamically add content and maybe even write your own search logic which respects those permiss…
We're working on switching to wordpress for the volunteer organization I work at. Right now all the "information/kinda static" content is on wordpress with pages and posts. Its a win, anyone with permission can edit. Our custom application isn't there and has its own separate database and code. We're thinking of moving the whole thing into a sort of plugin, but we're very symphony based.. Which we like
Re: The complicated futility of WordPress
#189I've too have been working with WordPress a long time. I built Quartz (qz.com) and The New Yorker (newyokrer.com) and other sites on WP. However so much of what this author says resonates more than I care to admit. I have a good relationship with WP but I worry about the future.
I remember doing a lot of work with customizations integrating WP and phpBB specifically, which ended up earning me an unreasonable amount money for a 16 year old. I have a certain fondness of WP but it’s heyday has long past coinciding with the abandonment of the independent internet. I greatly worry about its future mainly because it’s demise would represent the end of an era.
Perhaps the backlash to centralized social media will provide an avenue for a platform like WP to see a resurgence, but Automattic would really need to make a conscious effort to pivot with the changing times if they want to ride that wave. It won’t be the Wordpress as we’ve known it but (hopefully) the ethos remains. I wish them all the luck.
Re: The complicated futility of WordPress
#190Earlier quoted context omitted.
The issue is that if you’re developing like this on WP you don’t gain much from it except the ability to use a select few plugins and an admin UI. At this point why not use a solid PHP framework like Laravel?
I can answer this: because people do not want to pay for a developer, they want to pay for a designer. (It is exceedingly rare to find both in a single person.) The designer can, within the structure and strictures of Wordpress, build a site with all the whizzy things the client wants, and they can charge $X for it. A developer can do all of that as well, but they will probably need a designer as well (see above pare…