WordPress Philosophy seems to indicate that all design decisions are ultimately run by the user base to get a "democratic" voting of what changes to implement or reject. However, the reality is far from that. Is WordPress missing a "voting" system?
Including an autoloader within WordPress is not an all-or-nothing endeavour. With a few simple changes, we can have a fully functional autoloader being loaded with WordPress, and we can start refactoring the existing Core code to gradually load more and more classes (and even functions) through the autoloader.
Ryan McCue, Senior Engineer at Human Made and WordPress Core Developer, has posted a series of tweets regarding the fact that WordPress is far from an ideal platform for developers, which has spawned a lot of discussion.
As a long-form response to this, here’s a list of changes I would like to see in WordPress, and how I would try to address backward compatibility (BC) concerns. I don’t pretend to know that this is the absolute best way to tackle the problem, this is purely my own biased opinion, and how I would try to fix the issues if I were in charge.