The key is allowing non-technical folks to work without much training. I don't think anyone has found the right balance yet.
Since headless CMSes became popular 5-6 years ago (in large part thanks to Contentful), a lot of companies have moved to them based on the promise of separation of concerns, "omnichannel" publishing and better developer experience.
But what a lot of people missed was that a traditional CMS like Sitecore or Wordpress etc provides not only content management (for structured content) but also experience management (for pages and layouts). And in larger orgs, these two things are often managed by different teams, but both are driven by business users, not necessarily developers.
Headless CMSes typically only provide structured content management - by design - and so experience management ends up needing to be built into the consuming applications, which vastly increases their complexity (not to mention how you manage updates over time - developers now need to be involved), and that doesn't scale well.
Or it gets shoe-horned into the CMS as a less-than-ideal type of structured content, and becomes hard to manage by non-technical folks.
How do you see Tipe being used for experience management?
One of the problems with the WYSIWYG editor was that the developer effort typically added and extra 50% effort onto any task and like anything with Sitecore you ended up having to dig through PDFs on their development portal.
A slight aside though. One of the best things about Sitecore was its OOP approach to content. Every piece of content was an instance of a template. If you knew what you were doing with it you could build things very cleanly. I haven't seen anyone else implement anything similar in their CMS.