This way:

• there is no impact on people upgrading their platform (they don't need to reconfigure the engine if they don't need the feature)
• benchmark performance using the distro as is is not affected
• it is possible to use job priorities in a demo (i.e. priorities are assigned to jobs; however not used for acquisition which is probably not relevant)
• it is consistent with the defaults for jobExecutorPreferTimerJobs and jobExecutorAcquireByDueDate so that there can be one place in the docs where all the three features are described