@halikular @ocdtrekkie @autinerd @bagder That is not commercially viable. You're essentially asking to split a development team in two. And the team that does new things would be starved of resources because the team focusing on compatibility has much more work to do. Ironically, having it in one codebase and one team means you don't do *too much* of the compat work and you balance how much of that you should actually do.