First of all, it's far, far easier to write a plugin adding the "shiny" editor stuff to an IntelliJ Platform-based IDE. As far as the editor features are concer

First of all, it's far, far easier to write a plugin adding the "shiny" editor stuff to an IntelliJ Platform-based IDE. As far as the editor features are concerned, the only stuff Sublime does that would be non-trivial to implement in IntelliJ-based IDEs is multiple cursors - but it's still far less work than building an engine for all the smart stuff. Second, all the smart stuff has performance costs. As soon as you're building a complete model of the codebase and updating it in real time, you're losing all the low CPU/memory usage benefits of a plain text editor. Really, the only aspect in which we fell the pain of not being native is font rendering on Linux (which has a crappy implementation in AWT and there's little we can do about it). Other than that, it's not a problem at all to integrate as many editor features as you like into a JetBrains IDE.