←back to thread

172 points ValentineC | 7 comments | | HN request time: 0.903s | source | bottom
1. wkirby ◴[] No.41821631[source]
We no longer do custom WordPress work --- it turned out to never be worth the hassle --- but when we did, our company used ACF extensively. High quality plugin with responsive support and very fair licensing terms.

This --- to me --- smacks of complete bullshit.

replies(2): >>41821832 #>>41821884 #
2. xenago ◴[] No.41821832[source]
Forking it is whatever, but to take over their namespace and thus break trust across the ecosystem is a dealbreaker. All devs will have to move.
3. luckylion ◴[] No.41821884[source]
It is complete bullshit, but calling ACF high quality is also pretty out there.

It's one of those giants in WP that is stuck in the past, arguably much like a lot of core.

replies(2): >>41822261 #>>41825745 #
4. wkirby ◴[] No.41822261[source]
To be fair we haven’t worked with WP in 4 years; our experience with ACF was always positive.
replies(1): >>41822458 #
5. rasso ◴[] No.41822458{3}[source]
4 years ago it was still great. I had one contact with WPE support since they bought the plugin last year or so and it was the most frustrating support interaction I ever had. It felt like I was writing with an AI that was prompted to drive me crazy so that I would leave them alone.
6. bigiain ◴[] No.41825745[source]
It's certainly "high quality" in the sense of "it solves a huge number of requirements that WP core doesn't, in a way that's better that alternative plugins". It's a high quality WP Admin user experience. Just don't try looking too deeply into the database mess it creates.

For WordPress _users_, as in the people who log into the WordPress dashboard to run their website, 'stuck in the past' is often an advantage and not a bad thing. You'll be able to find blog posts and tutorials and youtube showing you how to use in, unlike the "new shiny" where there's no easily found example or support for.

replies(1): >>41826030 #
7. luckylion ◴[] No.41826030{3}[source]
I'm not arguing against its usefulness, not at all. The sites I work on use it as well (and abuse, you really shouldn't do complex things with it), though we're looking into replacing it with something custom because the dev experience is bad and the performance isn't great. But for the average small to medium site, it's great, especially because of what you mention: the standard use cases are super well documented by a million people having gone through them before you.

I wouldn't call it high quality though. 200k LOC even for the free version (I use pro), no OOP, global variables, bugs get no attention unless they're major. It was amazing when it first came out, but it has fallen behind even compared to core + other plugins (and the WP average is a very low bar).

It clearly belongs in core, just like 90% of Yoast's (or AIOSEO's, Rank Math') functionality, Redirection and permalinks, and they should have focused on getting that done instead of gutenberg. But also clearly this isn't the way to bring it into core.