4 ms·
> but I also do think that forking ACF into SCF was a net positive for the community. I think you can make the case that in principle this fork was a good idea
by dofm 28d ago
> but I also do think that forking ACF into SCF was a net positive for the community.
I think you can make the case that in principle this fork was a good idea. (Though I personally feel ACF is architecturally bad)
What I think is unarguable is that the way that fork happened, including the commandeering of the slug to pervert the auto-update mechanism, was both improper and self-destructive, and was pretty indicative of the impairment of Matt’s decisionmaking and seriousness.
- bedroom_jabroni 28d agoI agree, introducing it into the core should have and could have been a constructive move way before given how important the plugin is in the WP ecosystem. When and how it happened was a hilarious plot twist nobody expected.
- dofm 28d ago> I agree, introducing it into the core should have and could have been a constructive move way before given how important the plugin is in the WP ecosystem. There was a (stalled) core Fields API effort. The project lead abandoned core WP development ironically because of Matt's behaviour: https://make.wordpress.org/core/tag/fields-api/ https://make.wordpress.org/core/tag/fields-api/