he onus of success doesn't really rest on the XF devs anymore. It rests on the site administrator. If your site is doing badly, I hate to say it, guys, but it's probably your fault.
Yes and no. Obviously we all see the strengths of XF, otherwise we would use a different platform. On the other hand, your argument is a little odd: By leaving a lot of functionality to be implemented via add ons there is a lot of load and responsibility shifted over from XF to site administrators and a lot of additional complexity that they have to deal with: You have to find wether there is an add on, you have to configure it, so check for conflicts, bugs and updates and if there's trouble XF say: Well, not our problem. Plus you have the risk that no one asses the code quality of 3rd party apps and the developer may be responsive or not or one day even no longer support the add on you depend on. So, yes, the responsibility for forum success lies on the site admin (it always did) - but XF could do a lot of things to make their life easier.
If I understand the announcement for 2.4 this is the idea behind this update:
XenForo 2.4 will focus on quality-of-life enhancements for admins, moderators, and users alike. (...) As we have done with previous releases, we will be looking towards
popular suggestions when finalizing the feature set.
The interesting part is: When you look at the popular suggestions, sorted by popularity...
... 11 of the 15 top voted ones date back to 2010 (nincluding the "ignore" feature that we have been talking about earlier in this thread). What this means is up do individual interpretation:
• it may seem natual that older suggestions aggretate more votes as they had way more time to get them than new ones
• it may be that many other older suggestions have been implemented and these are just the ones left and they are left because they are to hard to implement or don't fit into the strategy
• it may be that due to the age at least some of the suggestions are not of real interest any more, outdated, and at least some of the people that voted for it are not interested in them any more or even no longer use XF
• it may be that suggestions are simply ignored when thinking about new features
• it may be that suggestions are not maintained (in terms wether they are for whatever reason ruled out)
• it may be that people stopped voting to suggestions b/c they felt they had no effect anyway
• it may be that the process of voting does not produce useful results (i.e. has generally a low participation)
or something completely different. I can't and won't judge. Someone recently wrote a brilliant truth somewhere in this forum:
Most users don't care too much for features once a very basic set it there. All they want is a space to communicate easily. It is more the administrators of the forums that are eager for features, not so much the users. Often more for their own playful attitude than for a real need and use.
I can unfortunately not remember who stated that and where, but I think that's true. If you install XF as it is and let it run there's not too much that forum users will miss and if so they can live with it. If as a site admin you start to customize you start a never ending journey down a rabbit hole and the deeper you get the more you loose contact to the basic functionality and overrate additional features. Often enough the best solutions don't have many features but few, but they have the right ones and focus on good usability.
Which brings me to next point: We all got used to how to administering XF. But I remember when starting with XF two years ago how dated it felt in the ACP in terms of looks, UX and administration (in comparison to younger software) and how cluttered and sometimes weirdly sorted the backend felt. W/o the search function within ACP and w/o the forum here (and the user manual) I would have been lost often (and sometimes this is still the case). Obviously you have to pay a price for flexibility and a high level of configurability - which is complexity of the backend. This is normal and even more if a product has a history and evolved over many years. And there are many products that are way worse than XF, to be fair. Still, some things are way more cumbersome than necessary. As a prominent example the need to use (s)ftp or alike to install or update add ons has been mentioned. But also simple things like i.e. a possiblity to filter/seach the list of installed add ons in real time (Ajax or similar). As some devs wildly add a [devname] before the add on name sorting is pretty wild and having to scroll a list of dozens is annoying.
Sometimes, when you configure something in a submenu point of the side panel and hit ok, the whole page including the sidepanel jumps up to the top of the sidebar and you have to scoll back down. Many options that you can configure in different places. There are a lot of things like that.
Possibly, if one would start from scratch today, UI and UX of the backend would be (way) different and some concepts would possibly be as well. But then again a complete overhaul and change of ACP would probably massively annoy long term users as they got used to it and would have to learn everything new.
So I really appreciate the idea of focussing on "quality of life" enhancements. Many add ons do that - things like the moderator panel by
@AndrewSimm are a life saver. Tiny add ons that i.e. allow scheduled posts or sorting of sticky posts or bigger ones like multi prefix are things that - in my opinion - should be in the core.
A very neglected area are custom fields: They are a great feature and I was totally baffled when I learned that they are easy to implement, but it is impossible to do much with them, i.e. a simple statistic based on custom fields is already impossible if you don't dive directly into the database and the land of SQL.
The lack of an integrated backup solution for the forum is another thing (no, not everyone has or wants C-panel) and a reliably GDPR compliant cookie-consent is another. There are really many areas where quality of life of site admins could be improved. Thus I think your statement...
truth is that the onus of success doesn't really rest on the XF devs anymore. It rests on the site administrator. If your site is doing badly, I hate to say it, guys, but it's probably your fault.
... really is a two sided sword.