which compounded
by a group of active developers whose number pales in comparison to that
of Firefox, means that reducing the strain on any one of them is an
overriding objective.
Even if that were the case, the plan breaks as soon as we run out of
existing active developers, if we fail to recruit enough new ones.
That's true, but the single most important lesson we learn from the
history of GNU Emacs is that this danger never actually materialized.
Which doesn't mean we should not try to recruit more, of course, it
just means that we shouldn't be too pessimist about this.