Is a Plain Textarea Good Enough to Learn In, or Do You Need a "Real" Editor?
The editor here is a textarea on purpose. Here is what that costs you, and what it buys back.
The editor on every challenge is a plain textarea with a line-number gutter, working Tab handling, and indentation that carries onto the next line -- not CodeMirror, not Monaco, none of the editor engines that power most "real" code editors. That is a deliberate choice, not a shortcut: a textarea is small, fast, and works with a screen reader with zero extra effort, where a heavier editor component would need its own accessibility work bolted on.
What a "real" editor buys you is syntax highlighting, bracket matching, and autocomplete -- genuinely useful once you're writing hundreds of lines across multiple files. What it costs beginners is a screen with more going on than the code itself, at the exact moment the goal is to think clearly about a dozen lines of logic.
Brian Kittrell, who built Coders Rock, started out on Notepad -- no highlighting, no autocomplete, no gutter, just text -- then moved to Notepad++ once line numbers and highlighting started to matter, and today works across several different IDEs depending on the project. That progression tracks the argument here pretty closely: the tool earns its extra complexity once the code you're writing has outgrown a plain text box, and pseudocode-and-challenge-length JavaScript hasn't outgrown one yet.
Press Run to see what your code does.
If a heavier editor ever gets added here, it will be because the challenges themselves need it, not because plain text looks unfinished. Nothing above needed highlighting to make sense, and that's the bet the whole console is built on.
Everything above runs in this page, on your own machine. There is more of it on the practice pages.