Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Why is WordPress considered to be poorly programmed? [closed]

Tags:

php

wordpress

I'm not a fan of PHP or spaghetti code, or anything like that, but in my experience WordPress works amazingly well, it's well organized, and I've never come across any hard to understand code. The documentation is incredibly thorough, any security flaws are fixed within seconds, and it "just works". Not to mention that it does EVERYTHING, and it has an awesome plug-in system. Oh, and "the Loop" is awesome. I've never had any problems doing simple modifications to the code or to themes.

Can you guys give any specific examples of what you don't like about it, or what you would have programmed differently? I just don't understand why it gets such a bad rap. I wish my own software worked as well and had as many features and looked as nice.

like image 297
Philip Brocoum Avatar asked Sep 26 '09 16:09

Philip Brocoum


People also ask

Why is WordPress terrible?

Why so many? Because the core software that runs WordPress is not designed to do all of those things. Each plug-in, even with the intent to make things run faster or safer or look cooler, adds bulkiness to your site. And worse — they add possible entryways for malware and hackers.

Is WordPress a good technology?

While WordPress started as a blogging tool, it has evolved into a powerful website builder and a robust content management system (CMS). The best part about WordPress is that it's easy to use and flexible enough to make different types of websites. That's the main reason why WordPress has grown so much in popularity.

Do you actually code with WordPress?

Despite being a no-code tool, a lot of professionals and freelancers make a living off of WordPress because they can code. So, you might know WordPress as a no-code tool – but some people are making huge money from it because they can code. This means WordPress is both a code and no-code tool.


2 Answers

I'm a fan of WordPress, but there are definitely issues that impede coders trying to work with it. As a small example, there's get_the_content() (returns) and the_content() (prints), but there's get_permalink() and the_permalink(). Then, there's just the_date(), because it accepts an argument indicating whether you want it to print or return. This kind of thing drives even an experienced WP person up the wall, because you've always got to be Googling the usage - and it speaks to a deeper lack of attention to detail in the code.

Another glaring issue is the lack of built-in caching. It even used to have it, but they ripped it out and never replaced it. You shouldn't need a third-party plugin to have basic caching in a system like WordPress, particularly with all the other bells and whistles it builds in.

To paraphrase (supposedly) Churchill, though, "WordPress is the worst blogging system... except for all the others".

like image 134
ceejayoz Avatar answered Sep 24 '22 09:09

ceejayoz


I've written many custom applications in PHP/MySQL over the years - from tiny to huge. Not having taken the time to learn the details of WordPress, I find it very frustrating to work with (under the hood).

Subjectively:

  • Very poor naming conventions
  • Execution flow is bizarre
  • General lack of organization
  • Hard to audit what happens when
  • etc...

Their concepts of usability is great, and support for plugins is also great. I'd just love to see the system re-engineered with those principles, but with a disciplined and clear development methodology.

I'm sure the next guy would say "no it isn't, bla bla bla", but that is just my opinion after bumping into it (hosting, modifying) about 3 times.

like image 31
gahooa Avatar answered Sep 23 '22 09:09

gahooa