I don’t have much to add to Emmanuel’s post.
The story is quite simple:
We got an idea for implementing a useful and powerful feature and then implemented it in record time of just few days. Meanwhile we noticed the planned ACF price increase. Our target was to release the new version on last Thursday, but couldn’t do it because we were still fixing bugs. Over the weekend we realised it would be good to let people know about the upcoming feature, so that they can take advantage of getting ACF. We used our social channels to do that.
Looking back, it would have been better to email users on Friday. Do and learn…
I think that professional use-cases PG and ACF PRO combo, create much more value than what they cost, even with new ACF pricing.
That said, we aren’t fans of this situation and understand that it puts the block feature out of reach of many users.
Still, using ACF lets us have this feature at all.
But we’re not married to ACF. If we find another approach that lets us support blocks and its implementation & support is feasible with our resources, we can do that.