So did I.
I have been using CP since it started with Scott Bowler and a dream.
Everyone knew there would be problems with plugins no longer working with CP down the line, and forked or new ones have been made to help mitigate that. But WP 5 has made this a nightmare.
All my sites run on CP and I have to use old plugin versions to keep them going. I even have to run old versions of my themes as well. It is obvious something needs to be done to keep CP 1.x viable.
The majority of CP users do not post in this forum and I rarely do either. Doing so usually results in being intimidated. Looking at the number of views on topics shows people are reading them, but keeping their mouths shut.
I even ran a site for a while that was dedicated to following CP and had a forum where non-geek people could feel relaxed enough to post anything. But still they did not post.
CP 2.x has always been the version that would be vastly different from WP. We were told we would be able to use 1.x indefinitely and it would receive security updates as needed.
The recent debacle with 1.4.0 showed how moving too quickly can cause major problems. There is no simple solution to 1.x’s compatibility problems and not enough developers to fork plugins.
I know nothing about how CP works at core level, but if it could be made to work with WP 5 plugins, then it would solve our biggest problem.
I have been thinking about moving back to WP, but the classic editor is not going to work for much longer. If Scott’s dream is to be realized, the compatibility issue needs to be overcome. We don’t need anything removed in 1.x - we need something added.