What? If there’s an actual standard, it will stop scripts from breaking, because the assumption that master is the main branch will always be true.

And yet not everyone used to use master, so scripts kept breaking for no good reason.

Either make it a standard, or stop assuming it’s a standard. De-facto isn’t good enough.

I like it, because it forced people not to assume master is the main branch. If something is common enough to almost be a standard, but it’s not actually a standard, it’s just waiting for disaster.

These assumptions cause unnecessary breakage, but people will make them unless forced not to.

No, it’s not that easy. Matt Mullenweg personally owns the plugin repository and has weaponized it by literally stealing paid plugins from their developers as revenge. You’d have to create an alternative repository for your fork to actually have a healthy ecosystem, but the individual developers are financially disincentivized to follow due to Mullenweg. This makes for a very uncertain future for both the project and the ecosystem - and why risk it, when there are better options?

Might be, you still shouldn’t build new stuff on there. It’s under the control of a person going through a mental breakdown and lashing out at everyone instead of getting help.

No longer after the drama of the last few months. Stay as far away from WordPress as is humanly possible.

They couldn’t log in because of the WP Engine checkbox