26

Fuck wordpress!!!!!!
Fuck it in the fucking ear!!!!!!!!

Wordpress is designed to be a blog - nothing more!
All the plugins in the world couldn't polish that grade-A turd!

Install a plugin, the theme stops rendering properly.
Fix the CSS to solve the issue, and another plugin fails.
Fix that plugin, then another one throws up errors.

Google for help, and you have to sift through a dozen suggested plugins that work around the issue, because that makes SO much sense.

"We have a problem, do we fix it?"
"Nope, just throw more fucking plugins at it!"
"Oh, what a good idea! Lets sell them too, thats even better"
"Oh yes, I'm so happy! We will profit from their misery"
"Hip hip hurrar! We are such amazing 1337 haxxorz, how much do we definitely not suck?!"
"We definitely don't suck, we're just amazing!"
"Does this mean we're full stack developers now?"
"Yes, it must do, we fuck site admins at every level in the stack!"
"Do you know what a stack is?"
"Nope, but we are 1337!"
"YAAAYYYY!!!"

It's just a mass of kludged code, written by script kiddies who think they are programmers because they can throw a few lines of PHP together.

The know NOTHING about convention, structure or rational design.

Everything about Wordpress is wrong, without exception.
It is the platform of hell, spawned from the piss and jism of satan himself!

In the time it's taken me to make this abomination of a platform behave correctly (i.e., work with HTTPS and stop sending unsecured content left right and fucking centre), I could have written a web app from scratch.

I've never detested a platform, its plugin library or its community of "developers" as much as this.

Wordpress can go fuck itself with a spade!

Comments
  • 5
    Oh, lovely. A plugin doesn't render the content in a table as it should.

    Suggested fix, disable all the other plugins.

    Because that makes sense.

    I wish I'd known about oxwall before I started this site.
  • 3
    Totally agree with you here.
  • 3
    @danharrin I'm using CMSMS for another site project, and it's lovely.

    Logical, straightforward, makes sense.

    Oxwall is a decent platform too - written with some coding convention in mind, and the code is readable and quite frankly beautiful.

    WP is a pile of turd. It's a mess to read, the community of developers (and I use that term in the most ironic way I can) are a bunch of wankers looking to make cash for inadequate plugins, and the stability and reliability is utterly lacking.

    Had I not committed so much time to it already, I'd rewrite it from scratch, but I'm near the end now and need to get the site live.
  • 4
    WordPress sucks... It's a given fact...
    Suggestion for future you: fail fast!
  • 0
    i don't think you should fuck anyone in the ear
  • 1
  • 3
    It's just a battle with it.

    You change some CSS, and it stops it loading.

    You examine the template and see that it doesn't enqueue the stylesheet properly.

    You fix the enqueuing in a child theme as you don't want to break it when it updates.

    The change knocks out something else, a plugin used by the theme.

    You fix that, and something else fails.

    it's like jenga - pull one brick out and the rest wobbles.

    Unregulated, uncontrolled plugin development has turned a once mediocre platform into an unmanageable mess!!!!
  • 3
    Instant fucking favourite.

    WordPress is a goddamn crippling cancer of the modern web.
  • 2
    Actually, the WP core isn't that bad, except that it's written in PHP. The real nightmare starts with the plugin and themes ecosystem, which is why wordpress.com itself doesn't allow that endless pile of shit.
  • 2
    Found the WordPress theme song
  • 2
    @Fast-Nop the core isn’t too bad now, but 4 years ago it was an absolute mess.

    The issue is that for so long php was entirely free form in how applications were constructed, and no coding conventions of any kind were enforced by the language.

    As a result, there are tens of thousands of shit plugins written with no structure to them, and enforcing proper compliance to an api would just break them and alienate users.

    It’s just gone too far to be fixable at this stage, unless you run a clean wp install with no plugins whatsoever.

    I read an article once which argued that wp was aimed at content creators and not programmers and that devs shouldn’t complain about it.

    I’m going to complain ;)
  • 0
    I'm forced to work in WP where I work, but I fix most of these issues by creating my own plugins and themes for most sites. Or using minimal plugins that I've used before and have fixes for the shit that doesn't work.

    Aside from everything already mentioned, not one developer knows how to enqueue stylesheets or scripts properly so you end up with 6 copies of jQuery, all different versions, all bogging down the browser and you're left with 15 second load times.
  • 0
    @sylar182 yup, sounds familiar! I won’t be using it for anything else after this.
    As it happens, I’m quite happy with woocommerce as a platform, it’s just the other plugins I’ve had to run with it that are doing my head in
  • 0
    Exactly. Turdpress does it’s intended purpose just fine. But when people were like “LETS MAKE IT DO EVERYTHING”, then it just started to suck.
  • 0
    I used to hate wordpress. Avoided it for first 8 years of dev career. Last 4 been working with it and actually grown to like it.

    Ive never seen any platform that doesn't require doesn't require effort and trade off.

    When they do make one, that's when the price we can charge goes riiiight down so don't wish too hard for this 🤣
  • 0
    I don't think theres anything wrong with wordpress itself (apart caring too much about backwards compatibilty, resulting in ugly core code)

    It's the community, and the shitload of retarded frontend devs that think they know how to program, that make up all the symptoms..

    I can develop fairly large wp sites without trouble, just because I avoid all the bloated plugins like YOAST and god forbid.... revolution slider.
  • 0
    Made my day.

    I run a team developing on a platform based on wordpress. Some previous turd of a developer decided it would be a good idea to use betheme AND visual composer AND revolution slider to "decrease time to market" or some other shit reason. Now we're adding a plethora of plugins that "extend" woocommerce, and I am actively thinking about and searching for my next job.

    By the way, woocommerce. They moved to composer, by which I mean they moved they main class to the includes folder so it would be autoloaded, but left ALL of the require_once calls in there. Why bother?
  • 0
    You mean Drupal, right?
Your Job Suck?
Get a Better Job
Add Comment