WordPress and it's fucking buggy themes and dashboard, fml ,only God knows why on earth I decided to use this pile of shite wordpress.if I could I would have migrated to another CMs I would have done so long time ago.Wordpress,you are wasting my life away having to manage a website with your buggy shit.

I'm going to write this to everyone who says either good or bad things about Wordpress:
Whatever you think of Wordpress right now, your current opinion will fade into nothingness after you realize what it's made of, and will likely become much worse.

Go to wp-includes/functions.php and read the code. Take a good thorough look. Analyze it. Realize what you're looking at, what it represents, what it encompasses, and how it's named. Imagine yourself writing that code and posting it as an open source project.

@AndSoWeCode well.. It is WordPress.
It's literally a plethora of bad practice and lessons in what not to do.

Sometimes I wonder if they avoid namespaces & reflection on purpose.

@AndSoWeCode I know WP was crappy to work with, but didn't know it was crappy on the inside too. Why so popular doe? It's kinda amazing that sooo many ppl use it

@AndSoWeCode can you explain this a bit? Do you mean this in a positive or negative way?

I had a look at it and was, except for the unhandy PHP code, surprised how well documented it is.

@ctwx The best documentation is the one you don't have to write. If the code is half commentary then there's something seriously wrong with the code. And that thing which is wrong is the entire code.
* No code file should EVER be bigger than 2000 lines. Even 2000 is huge, but still a solution in some cases.
* No code file should EVER be called "functions", nor "helper1", nor any other bullshit. It doesn't explain what it does. And if it does everything, then it doesn't do anything.
* No software that is developed in 2017 on a platform that supports OOP, should ever be written using mostly global functions. It's disorganized and BAD.

Why all that? Well because you don't know what data structures you have to pass or get as a return unless you run the code or read very long documentation. You don't know that just by reading the code, which is unacceptable. Code should be self-explanatory. If it's not - kill it.

@AndSoWeCode sure self explanatory code is the best but some parts may need some explanation.

But all in all I agree with you. Thanks