I am a developer with a passion for testing. I've been coding for 14 years and I want to share my experience and learnings with other developers to help them write better software.
In some situations people definitely won't change because they're scared or because it is difficult.
Making a significant update to a widely used tool is always going to be controversial. And I suppose you have to expect the developers of the 'change' are going to defend their decision. Even if ultimately their decision was a bad one.
My main gripe with WordPress, if you exclude all the legacy and security issues, is they have refused to integrate with Composer in any way. So more and more developers are hacking together WordPress / Composer based solutions which will ultimately undermine the WordPress project entirely unless WordPress embrace Composer.
As your post highlights it's clear a number of splits are beginning to occur in the community.
I am a developer with a passion for testing. I've been coding for 14 years and I want to share my experience and learnings with other developers to help them write better software.
In some situations people definitely won't change because they're scared or because it is difficult.
Making a significant update to a widely used tool is always going to be controversial. And I suppose you have to expect the developers of the 'change' are going to defend their decision. Even if ultimately their decision was a bad one.
My main gripe with WordPress, if you exclude all the legacy and security issues, is they have refused to integrate with Composer in any way. So more and more developers are hacking together WordPress / Composer based solutions which will ultimately undermine the WordPress project entirely unless WordPress embrace Composer.
As your post highlights it's clear a number of splits are beginning to occur in the community.
ClassicPress is embracing composer - for a start you will be able to install ClassicPress using it
Well that would be a step forward.