Only a monumental idiot tries to pass off the prime example of how to write PHP badly as their own. It was a lousy blog script in 2004 and hasn't improved (nor actually become a CMS) since.
Only if your criteria for "better" is entirely based on shortness of learning curve. Drupal has always been more of a framework than a CMS, long before the likes of Cake, CodeIgniter, and Laravel.
WP's only advantage is letting designers pass themselves off as developers. It has a terrible database schema, the code is insecure spaghetti, and it's all held together with bad practices.
Drupal has always been more of a framework than a CMS, long before the likes of Cake, CodeIgniter, and Laravel.
WP's only advantage is letting designers pass themselves off as developers. It has a terrible database schema, the code is insecure spaghetti, and it's all held together with bad practices.
Again, I couldn't disagree more. Having used both for years, it's Drupal that's the insecure mess these days (Drupalgeddon I and II, anyone?), and it's just plain dwindling. It was hard enough to find useful modules for it, and every new version sees fewer. I used to push for it as a CMS of choice for clients, but not for about five years now. It's just too much of a pain, and all too often can't do what needs to be done anyway (without doing it all from scratch).
Only a monumental idiot tries to pass off the prime example of how to write PHP badly as their own. It was a lousy blog script in 2004 and hasn't improved (nor actually become a CMS) since.
WordPress has continually improved, and is now quite nice. It is indeed a full featured CMS, can even be run headless if you like (has an API), and is very nice to write custom plugins for.
I've used it off and on since it started out, programmed plugins for it quite a bit in the last few years, and watched it improve a hundred-fold. Anyone who tries to say that it's no better than it was in 2004 isn't a serious commenter.
Oh yes, and 2001 will be year of the Linux Desktop because Windows is antiquated garbage! Wordpress has a dominating market share and a practical monopoly on the ecosystem of templates, plugins, etc. Whether or not it's a prime example of bad PHP is completely irrelevant.
A ton of dominating software is poorly written, ask people working at Adobe, Microsoft, Oracle, SAP etc. It just comes to show that people that vote with their wallets don't care about programmer pet priorities such as code quality.
I would argue PHP hate has become antiquated garbage. No offense, but who would mod this comment "interesting?" PHP is not my first choice for a programming language, and it is never been the latest greatest fad, but maybe that's a good thing. People use it to build websites, and those websites work. And as I said in another comment, git clone WordPress's core sometime. Read the code. I think you might change your mind.
Systems programmers are the high priests of a low cult.
-- R.S. Barton
WordPress is antiquated garbage (Score:5, Insightful)
Only a monumental idiot tries to pass off the prime example of how to write PHP badly as their own. It was a lousy blog script in 2004 and hasn't improved (nor actually become a CMS) since.
Re: (Score:1)
Re:WordPress is antiquated garbage (Score:4, Informative)
Only if your criteria for "better" is entirely based on shortness of learning curve. Drupal has always been more of a framework than a CMS, long before the likes of Cake, CodeIgniter, and Laravel.
WP's only advantage is letting designers pass themselves off as developers. It has a terrible database schema, the code is insecure spaghetti, and it's all held together with bad practices.
Re: (Score:3, Interesting)
Drupal has always been more of a framework than a CMS, long before the likes of Cake, CodeIgniter, and Laravel.
WP's only advantage is letting designers pass themselves off as developers. It has a terrible database schema, the code is insecure spaghetti, and it's all held together with bad practices.
Again, I couldn't disagree more. Having used both for years, it's Drupal that's the insecure mess these days (Drupalgeddon I and II, anyone?), and it's just plain dwindling. It was hard enough to find useful modules for it, and every new version sees fewer. I used to push for it as a CMS of choice for clients, but not for about five years now. It's just too much of a pain, and all too often can't do what needs to be done anyway (without doing it all from scratch).
Re: (Score:3)
Only a monumental idiot tries to pass off the prime example of how to write PHP badly as their own. It was a lousy blog script in 2004 and hasn't improved (nor actually become a CMS) since.
WordPress has continually improved, and is now quite nice. It is indeed a full featured CMS, can even be run headless if you like (has an API), and is very nice to write custom plugins for.
I've used it off and on since it started out, programmed plugins for it quite a bit in the last few years, and watched it improve a hundred-fold. Anyone who tries to say that it's no better than it was in 2004 isn't a serious commenter.
Re: (Score:2)
Oh yes, and 2001 will be year of the Linux Desktop because Windows is antiquated garbage! Wordpress has a dominating market share and a practical monopoly on the ecosystem of templates, plugins, etc. Whether or not it's a prime example of bad PHP is completely irrelevant.
A ton of dominating software is poorly written, ask people working at Adobe, Microsoft, Oracle, SAP etc. It just comes to show that people that vote with their wallets don't care about programmer pet priorities such as code quality.
Re: (Score:3)
I would argue PHP hate has become antiquated garbage. No offense, but who would mod this comment "interesting?" PHP is not my first choice for a programming language, and it is never been the latest greatest fad, but maybe that's a good thing. People use it to build websites, and those websites work. And as I said in another comment, git clone WordPress's core sometime. Read the code. I think you might change your mind.