Great write-up, Rafal! I really like how you connected APEXlang, Git, and merge workflows in a practical way.
I think the “APEXlang instead of Working Copies” point is directionally right for Git-first/file-based workflows, but a bit more nuanced in practice. It is not one or the other, but using them together.
In a shared APEX dev environment, Working Copies still matter for isolation, main-app protection, and APEX-owned merge flows. APEXlang changes the game when Git is the source of truth, especially with isolated dev environments or per-branch databases, but full export/edit/import against a shared app can still overwrite other developers’ changes unless locks or process controls are in place.
Martin and I are doing a Kscope session this year where we touch on this topic, “Revolutionizing APEX Development with APEXlang and CI/CD.” We’ll cover APEX-first vs Git-first workflows, Working Copies, shared dev environments, and where APEXlang changes it. Hope to see you there!