core-ai-bot
commented
3 years ago 
@ilsken - thanks for your input. At this point I think it's highly unlikely we would switch to ACE. To address some of your notes:
- I would guess (although I haven't looked into it) that writing something to convert TextMate/Sublime themes to CM themes shouldn't be a big deal--i.e., there shouldn't be a deep architectural reason why this would be difficult to do. Have you encountered anything that suggests this would be difficult?
- There's an active branch/pull request for adding multicursor support to CM: https://github.com/marijnh/CodeMirror/pull/1656
- CM's coding style is definitely different from ACE, but over time the code has proven to be understandable, malleable and extensible. Overall,
@marijnh has been very responsive to bug reports and requests for new features, while still keeping the core relatively simple and pushing ancillary functionality out to addons.
Also, note that we would need to add inline editor support to ACE--again, that's not impossible to do (I had a prototype of it way back when we were first evaluating ACE vs. CM) but it's nontrivial work.
So, it's not clear to me that there are enough advantages to switching that it would justify the work. That said, if you're interested in forking and trying it out to see how it works, please feel free!
ACE editor now uses a BSD license (licensing as I understand was the original reason for the switch). Moving back to ACE would have a few advantages
I've been considering starting a fork that replaces CM with ACE, just wanted to see if there'd be any interest. Personally I think it'd be a huge plus if developers can use the themes and features they are already familiar with in sublime/textmate/etc and have an editor that will be actively developed and maintained for a long time (CM is very active but I'd say there's a higher chance of ACE remaining in active and fast development just because of the bigger team and what it's developed for)