As you can see, we are working on it: https://github.com/orgs/joomla/projects/51/views/1
We fully agree with you regarding this and we are as angry as you about the current situation. Normally all occurrences in the core code should have been removed when the code was deprecated, but that was fumbled before Joomla 4.0. We are doing the cleanup for this and have been for the last few years. Doesn't get easier when no one tests those PRs though.

@Hackwar Ok, thanks 🙂
So will that deprecated stuff be removed before the release of J6.0?
If not, I guess it will all need to wait till J7, as those will cause B/C breaks.

Depends on how many people work on it

We are working hard on removing everything in time, but some stuff will indeed be postponed to 7.0 or even later. For example the LegacyErrorHandlingTrait will be removed in several steps. We'll remove it from some classes first and use the new exception flag wherever possible. Then we will remove the usage from the core classes in 7.0 and we might delay deleting that trait until 8.0. that last part is not decided yet. Lots of other deprecations will be fixed in the coming days with the updates to the Joomla Framework to version 4. One of the bigger changes will be to move the logic from the static helper classes to the respective models and to use the helper classes only as proxy to the models then. That is something which we most likely won't get done (completely) before 6.0.

@Hackwar Ok, thanks 🙂
So will that deprecated stuff be removed before the release of J6.0?
If not, I guess it will all need to wait till J7, as those will cause B/C breaks.

It would be super helpful if you could help here and clean up one or two (or more) deprecations 🙂

@bembelimen Sorry, was just here to ask the question.
I won't get involved in core code (anymore) for personal reasons.