I didn't write drastically. In addition:
I didn't write a huge team either.
Using the "nine women" analogy for a mature software platform is a classic logical fallacy. That analogy refers to sequential tasks that cannot be partitioned, implying that software development is a single, indivisible linear process like pregnancy. It is not.
Software development consists of hundreds of distinct features, bug fixes, and infrastructure improvements that can be parallelized. While 9 women can't produce a baby in a month, 9 developers can certainly build 9 different features in the time it takes 1 developer to build them.
We aren't trying to birth a single baby here; we're trying to run a nursery, a school, and a hospital simultaneously. Trying to do that with a skeleton crew isn't "efficiency" — it's negligence. XF isn't suffering from "too many cooks," it is suffering from a complete lack of capacity to work on parallel streams.
No, and I don't care. If they present features from a new version but only release it a year (or more) later, it means something is lacking in the process. They might call it 'upstream development delay'; I call it a lack of progress.
Yes, but if you want to slow down updates, you don't publish "Have You Seen" features a year in advance and say 2.4 will be released ASAP (six months ago). You are misreading the map again. Their business model is to make money. Not updating your software in a timely manner, or worse, saying you will update it but failing to do so, is not good business practice. It does two main things:
- It basically destroys customer trust in the product and the brand overall.
- It greatly delays license renewals, which I guess is a very big chunk of XF's business model.
Actually, it's the other way around. The more features included in the core, the fewer headaches large forum owners have in general.
Good. If cloud services are the main focus, they should just shut down the self-hosted licensing entirely. Currently, in my opinion, it does more harm than good.