Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
@AlmondSauce Let's put it this way:
Install WordPress using a webapp installer. Add template bought from Envato. Add JS Composer. Add tons of other plugins. Done! Easy! Open Solitaire and pretend like you're still working hard.
Then the site is slow as fuck, takes up all memory on the server, has lots and lots of security holes, gets infected with every worm imaginable, can't be upgraded because the template and/or plugins are unmaintained crap…
“But it's not our code! You must have configured the server like shit, it's all your fault! Throw more RAM at it or something.” -
@ethernetzero Exactly. When scenarios like that happen on nearly *every* site I've seen that uses Wordpress, I just don't see how the common consensus is still "oh, just use Wordpress, it'll be great!"
It's analogous to everyone building houses from cardboard because it's quick and easy to work with, seeing that they all fall down after a month, then saying: "Ah, would you look at that! Still, can't be our fault, owner must have been too fat or something. Never mind, on with the next cardboard house!" -
@AlmondSauce The way I see it, there are two main causes:
1. People don't want to learn new things or change their methodology. They chose WordPress because of the buzz, then stayed on it because they don't even want to know of any alternatives.
2. People only care about building the site, not maintaining it. Maintenance isn't even in the picture for most of them.
That's why WordPress keeps being recommended left and right for everything, no matter if there are better suited tools or not. -
@ethernetzero In this particular case, it was neither.
Marketing just wanted a quick campaign site, for which it's totally fine to use WP (we cannot ask them to edit *markdown* files, can we?)
Then the thing turned into their main website with full backing from the mothership corpo, quickly establishing itself in the "elephant traffic" category.
Also note this happened quite a while ago before the hipster go-rust-node static site generator mania, when django was just a giant security hole and nobody had time for RoR.
So there you have it: WordPress
Of course the shouting episodes all happened during the era I was doing WordPress dev.
So we were a team of consultants working on this elephant-traffic website. There were a couple of systems for managing content on a more modular level, the "best" being one dubbed MF, a spaghettified monstrosity that the 2 people who joined before me had developed.
We were about to launch that shit into production, so I was watching their AWS account, being the only dev who had operational experience (and not afraid to wipe out that macos piece of shit and dev on a real os).
Anyhow, we enable the thing, and the average number of queries per page load instantly jumps from ~30 (even vanilla WP is horrible) to 1000+. Instances are overloaded and the ASG group goes up from 4 to 22. That just moves the problem elsewhere as now the database server is overwhelmed.
Me: we have to enable database caching for this thing *NOW*
Shitty authors of the monstrosity (SAM): no, our code cannot be responsible for that, it's the platform that can't handle the transition.
Me: we literally flipped a single switch here and look at the jump in all these graphs.
SAM: nono, it's fine, just add more instances
Me: ARE YOU FUCKIN SERIOUS?
Me: - goes and enables database caching without any approvals to do so, explaining to mgmt. that failure to do so would impair business revenue due to huge loading times, so they have to live with some data staleness -
SAM: Noooo, we'll show you it's not our code.
SAM: - pushes a new release of the monstrosity that makes DB queries go above 2k / page load -
...
Tho on the bright side, from that point on I focused exclusively on performance, was building a nice fragment caching framework which made the site fly regardless of what shitty code was powering it, tuned the stack to no end and learned a ton of stuff in the process which allowed me to graduate from the tar pit of WP development.
rant
wordpress sucks
wk125