How Editora compares
Editora does not try to replace every editor for every person. This page covers where it differs, where it does not, and what we measured.
Startup, measured
These measurements were taken in July 2026 on Editora 0.9.9, not the current release, and have not been re-run since. Both tables are the median of timed runs on one Apple M5 running macOS 26.4.1, with every editor fully quit between runs and launched the same way. The clock starts at launch and stops when the editor window showing the file or project appears.
Opening a single file
| Editor | Median | Range |
|---|---|---|
| Editora 0.9.9 | 1.49s | 1.40s to 3.64s |
| VS Code 1.125.0 | 1.49s | 1.23s to 2.24s |
| IntelliJ IDEA 2026.2.0.1 | 5.60s | 4.99s to 7.70s |
Five runs each, opening a 710-line Markdown file with no project loaded. Editora and VS Code are level here; the difference between them is two milliseconds, which is noise.
Opening a project folder
| Editor | Median | Range |
|---|---|---|
| Editora 0.9.9 | 2.29s | 2.21s to 2.63s |
| VS Code 1.125.0 | 2.92s | 2.60s to 2.99s |
| IntelliJ IDEA 2026.2.0.1 | 7.33s | 6.17s to 8.88s |
Three runs each, opening a 137 MB source repository. Treat the gap between Editora and VS Code as indicative rather than settled: repeat sessions of the same test moved Editora's median between 1.40s and 2.29s, a spread wider than the gap itself.
How the measurement works
Each editor is quit, the machine is left to settle, then the app is launched with the file or folder as an argument. A watcher polls until the application owns a window whose title names the file or project, and that is the moment recorded. A discarded warm-up run precedes the timed ones, so every editor is measured with a warm page cache.
Waiting for any window would be easier, but it would give the
wrong answer. IntelliJ puts up a window called splash well before its editor is
ready, and timing that would have understated its 5.60s by several
seconds. Matching
on the window title is the only definition that means the same thing across
an Electron app, a JetBrains IDE, and a JavaFX app.
These numbers are not a cold boot, a measure of when indexing finishes, or a claim about how any editor performs on your hardware. They are relaunches on one machine, and all three editors continue working in the background after their window appears.
Where each one is strong
| Editora | VS Code, IntelliJ, Emacs | |
|---|---|---|
| Keybindings | Five complete keymaps (Emacs, CUA, Sublime, VS Code, IntelliJ), every command rebindable | VS Code and IntelliJ ship keymap extensions for each other; Emacs is its own thing entirely |
| Reaching a command | Everything is a registered command with an id, reachable by chord or fuzzy M-x search. No hidden actions | VS Code's palette is close in spirit. IntelliJ hides a lot behind menus and dialogs |
| Interface range | Four modes in one app, from Zen (bare text) to a full IDE, each a palette command away (Zen and Expert also have a chord in the Emacs keymap) | VS Code and IntelliJ both have a Zen/distraction-free mode, but no equivalent spread |
| Language support | 23 language servers (Beta, switched on in Settings), using the ones already installed on your machine | VS Code's extension marketplace is far larger. IntelliJ's Java and Kotlin tooling is deeper than anything here |
| Account and telemetry | None. No sign-in, no usage reporting, no subscription | VS Code collects telemetry by default (it can be turned off). IntelliJ Ultimate is a paid licence |
| Extensibility | A plugin API and a signed registry, small by comparison | Tens of thousands of extensions for VS Code, a mature plugin market for IntelliJ |
When Editora is probably the wrong choice
- You want a specific extension. Editora's plugin registry is small, and VS Code almost certainly has what you are looking for.
- You do heavy Java or Kotlin refactoring. IntelliJ's static analysis and refactoring tools go well beyond what a language server exposes.
- You already have a tuned Emacs configuration. Editora borrows the editing model, not the extensibility; nothing here replaces Elisp.
When it fits
You keep your hands on the keys and want every action to be a command you can find or rebind. You want language servers, a debugger, git, and live previews without an account or a subscription. And you want an editor that can be a bare page for writing and a full IDE for the same project ten seconds later.