We talked about this a bit in the last town hall:
Yeah- CKEditor has to go in the big picture. Some PE firm has bought it (and TinyMCE too) and is doing what they can to moneitize the editor space. More power to them, it’s not an easy problem to solve and it’s a bit weird that we’re all going to depend on these editors for countless SaaS apps yet expect them to be free. That said, the approaches they’re taking with their core license kinda make it a non-starter for a MIT licensed open source cms like us to include it. It’s a shame, as I’d be perfectly happy to upsell their extensions - but here we are.
There’s already been some prototyping of different approaches with v10.
We also know that we need to at least leave the LTS version of CKEditor that we do have rights to distribute in there for a while as there are any number of extensions that use it in hard coded ways.
Our vision for v10 would be a new default editing experience, but being careful to try our best to not bork old solutions that work.
I would expect the same to be true for bootstrap, LESS, and frankly any other approach we have in the core today. The focus for v10 is to fix bugs, update dependencies, and deal with the CKEditor issue. A combination of polishing the last 10% and trying to buy some long runway for future version support.
There’s always talk of exciting new template engines and what not, but to be direct - we need Concrete to work the way Concrete works. It’s more important to me that existing projects that depend on it behaving in a certain way can continue to work over embracing whatever is the new front end hawtness. Such is life.