No one is disagreeing there are bugs such as these. No one is disagreeing that they detract from initial experience of starting with Plone.
If something is wrong you have several choices. You can
a) fix the problem yourself
b) report the problem
c) whinge about it, and how nothing is good anymore and chastise the community at large
d) consider constructive ways to improve the community to get the mutually desired outcome. Work towards implementing these.
I know I've done my fair share of option (c) too but I've also tried really hard to do a lot of (d) (and a and b too).
I took over leadership of the UX team a few years ago to try and fix the issues around focus on UX and onboarding. I've worked on proposals about changing the PLIP process and strategic summits to be more focused UX. I've even tried to change our bug documentation process to create a more UX focused process via github issues. These efforts didn't work (obviously) but watch any of my plone conference talks on youtube if you don't believe me.. Trying to tell me I'm not concerned about user experience of Plone makes me consider you haven't considered the end user experience of how and to whom you are directing your anger and also what you think will be the end result of your rants?
My point is, this is a hard problem to solve, but as I've found in the past, getting angry about it and accusing other volunteers doesn't help either. We are an under-resourced community where the majority of members have very technical interests. This is not unusual for open source. UX is hard and even harder for developers. It does require strategic vision and leadership to steer developers from shiny things, to things that that seem less interesting but will benefit their income more in the long term. But my question is, do you have any ideas on how to fix this situation? Because I am 100% behind any new suggestion you have.