Why can't we use static objects?

Why not? proper implementation cant be bad, where-areas many developer (beginners) are using very poor auth system and also many devs just stopped using CI.

namespaces are very desirable in CI 4.0, even if it mean CI becomes more complicated for the first-time user.

well, first-time user this days learn Laravel or Symphony or Yii :=D

I wrote a long reply (rant) to this and my system crashed before I could post it...
So, this is the short version, still a rant:

Three choices:
1) Third-party auth system(s) (my personal choice and the developers choice).
2) Basic auth system built-in to CI core or library.
3) Full feature auth system, again built-in to CI.

#2 has the problem of being too simple and giving the false impression of being sufficient.  First time developers find that it will not meet their needs and complain about it later.  Most of use have written these simple auth systems and, I assume, either re-wrote them or installed a third-party, full feature system because it saved time and money.

#3 is both bloat and is limiting on the features offered.  A case of "Do it the CI way or the highway".  I want choices, not one-size-fits-all.  

RE the three other frameworks you cite, yes, I use a couple of them, but come back to CI when I want to work faster and make a smaller footprint application.   Yes, there is a steeper learning curve for those other frameworks, and some (first-time coders?) are willing to spend that time and money.  CI is better, because you can choose the features (third-party or home-grown) to integrate. 
[shorter rant off]

Please don't take this personally, it is about the work we do to make a living.

CI 3.1 Kubuntu 19.04 Apache 5.x  Mysql 5.x PHP 5.x PHP 7.x
Remember: Obfuscation is a bad thing.
Clarity is desirable over Brevity every time.