I'd say its better to have the first version of such a huge change on a STS version, so you can fix any conceptual issues quickly. LTS should be stable.

i understand that point of view, but releasing an LTS with a dead technology is imho also not a very good thing to do.

Optimal would have been new backoffice in 12, and then stabilize in 13, but that was obviously not possible 🙂

That was my biggest motivator to move from 10 to 13, we typically skip the STS, due to a lot of work to convert all the projects to the latest versions. But still having the AngularJS in there is a bummer 😦

If the new backoffice came out in 13 I would be so nervous to recommend it to clients. There would be hardly any packages ready for it and it could be a big flop. Releasing it in 14 (STS) gives them time to refine it and by the time 17 (LTS) is out there will be more packages available and more confidence in it.

Also it gives more time to convince them to add Blazor as an option... I'll get my coat 🤭

Blazor is already an option, you just need to run it in a webcomponent

I'm aware, I'm just causing trouble. Todays 24 Days in Umbraco (I know it's front end) has got me thinking about getting back into Vue again as well.

I must admit, I was quite relieved what I saw the news (way back when) that Bellisima was pushed back to v14. I wouldn't have recommended building on v13 with all the changes and lack of initial packages. This release gives us that breather and added security of a stable release for new sites and support before all the fun begins.