161–170 of 229 posts
A sane framework might specify the URL(s) once in a config file and/or DB field, but ultimately leaving that side to the web server configuration where it belongs.
After that you can get into all the other issues people are talking about already.
WordPress is the most giant bowl of spaghetti code in existence ever! One must wonder not why the market share is shrinking but why it is still a thing! Not only it's buggy and hard to scale, but it's also costly! All the freemium plugins become very expensive! A nonprofit I was involved with had to pay thousands per year to keep an essential WooCommerce match at least 10% of the functionality of Shopify, which comes…
> A nonprofit I was involved with had to pay thousands per year to keep an essential WooCommerce match at least 10% of the functionality of Shopify Sorry but I don't believe that for one second.
WordPress is the most giant bowl of spaghetti code in existence ever! One must wonder not why the market share is shrinking but why it is still a thing! Not only it's buggy and hard to scale, but it's also costly! All the freemium plugins become very expensive! A nonprofit I was involved with had to pay thousands per year to keep an essential WooCommerce match at least 10% of the functionality of Shopify, which comes…
I have experience with both shopify and woocommerce and the difference is WooCommerce can be free if you spend the time or use free plugins. You can do anything with WooCommerce you can do somethings with shopify. Shopify has a base cost plus additional costs for anything but you can dump money on both. Most of the frameworks and open source software is written by amateurs.
Earlier quoted context omitted.
I host a hobby website and use WordPress for everything. Even as an entry level user, I agree the amount of plugins are ridiculous. But it's free and I only pay for hosting. Anyone knows what are the alternatives for someone like me?
I've been looking at replacing my project's website with Hugo ( https://gohugo.io ). Rather than generating a web page dynamically every time someone comes to your site, you generate the entire website statically whenever you change something. That means hosting can be entirely a "dumb" web server (or a "dumb" web server + apis which feed info to javascript, if you really need it). It also means: * you can keep every…
We can make assumptions all day but for me, the worst thing about WordPress is EASILY Plugin Hell. I can update all plugins this morning and they all want updates by the end of the day. And then when they break it’s a disaster. WordPress itself needs to take a chill pill too. Leave a version out for a year or more, and only small security patches. In the last year, I think we’ve seen block widgets, JQuery migrate nig…
The WordPress codebase is a disaster, and the problem is self-compounding. The founders / core have found success writing disastrous code, and as such have no impetus to be aware of the benefits of higher quality - this is largely because (as you point out) the model of development shifts the burden to small individual website makers deploying (& maintaining / firefighting) WordPress.
Since it's open-source, a disastrous codebase could be "fixed" over time if experienced engineers were willing to join and contribute to the project over time, but the culture of QA-ignorance among existing core contributors has a tendency to exasperate experienced engineers.
I'm not saying it's a "toxic" culture per se - it's very open, and especially welcoming of new / inexperienced / beginner contributors, which is certainly cool for learning. But once contributors gain a little knowledge they go one of either two ways: knowledge-stagnation (enough to contribute but not to improve), or exasperation (enough to know how to improve but lacking motivation to make that uphill battle).
The culture from core extends to the plugins, not only because there's overlap in devs, but also because the APIs the plugin community have to use are garbage. This means many of the popular plugins - while they may have high-quality UX and design - have very poor code behind that.
All the above means that WordPress needs constant small fixes contributed by an army of devs to prevent it falling over / getting hacked, which massively increases the update frequency: there's nothing preventative within it's architecture, it's all reactive patches. It also means it'll only be a viable platform as long as its extremely popular: once popularity decreases a little, the maintenance burden will be far too high for the smaller community to sustain, and existing installs are going to be even more vulnerable than ever.
The only people I know who hate Wordpress are the developers who have had the misfortune of having to manage an instance of Wordpress. All the marketing and content people I have worked with love it.
The only people I know who hate Wordpress are the developers who have had the misfortune of having to manage an instance of Wordpress. All the marketing and content people I have worked with love it.
Wordpress code base is the best argument for the MVC design pattern specifically because it shows what goes wrong when you toss the idea of encapsulation out the window.
I think the "private website" space is shrinking - despite what adverts for Wix and Squarespace might infer. The consumer/blog space of geocities, tripod and the like went to social media. Then we went through a period of "businesses putting up 10 pages for a fixed price" through first of all "a local web guy" then by themselves using Wix/WP/SS etc. I've just had a bathroom fitted by a guy who functions purely on Ins…
I was previously a PM at a company where I got to interview a lot of content creators on various platforms (YouTube, Instagram, TikTok, etc). Specifically creators with large enough followings where it was their sole source of income (typically $1K-$10K per month). I was initially shocked by how few of them had personal websites, but they're able to get by with the tools that the platform provides them. They didn't s…
We can make assumptions all day but for me, the worst thing about WordPress is EASILY Plugin Hell. I can update all plugins this morning and they all want updates by the end of the day. And then when they break it’s a disaster. WordPress itself needs to take a chill pill too. Leave a version out for a year or more, and only small security patches. In the last year, I think we’ve seen block widgets, JQuery migrate nig…
Earlier quoted context omitted.
Well I guess chances I will ever use Squarespace, Wix or Wordpress: ~0%. But I'm not sure what that adds to the conversation without some background context on our requirements, use-cases or constraints?
There’s literally a market for extracting data from those platforms so people can move to more flexible solutions that they can control and extend.