[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f28yy7fm2o5d77":3},{"code":4,"message":5,"data":6,"timestamp":45},10000,"success",{"full_name":7,"position":8,"description":9,"language":10,"stars":11,"forks":12,"stars_gained":13,"age_days":14,"hn_threads":15,"one_liner":16,"summary_md":17,"topic":18,"github_topics":21,"license":41,"homepage":42,"updated_at":43,"history":44},"eugenioenko\u002Fttt",15,"TTT Editor (Terminal Text Tool): A real alternative to VS Code, Zed, and Sublime that runs in your terminal. A TUI that feels like GUI. Single binary, zero config.","Go",831,94,211,281,[],"A terminal code editor for developers who want IDE-grade editing (LSP, multi-cursor, git) without leaving the shell.","## The problem\n\nTerminal editing usually forces a choice: Vim\u002FNeovim with a config and plugin ecosystem to assemble, or a GUI editor (VS Code, Zed, Sublime) that pulls you out of the shell and into a separate window. TTT aims at the middle ground — a full-screen TUI with the editing affordances people expect from a GUI IDE, shipped as one Go binary with no configuration required.\n\n## What's different\n\nThe distinguishing bet is breadth of GUI-style editing inside a terminal: multi-cursor with select-next-occurrence, code folding, split\u002Funified git diffs that update as you type, inline git blame, and LSP-backed completion, diagnostics, signature help and formatting. Syntax highlighting comes from the author's own pure-Go TextMate port, which the README claims handles multi-line constructs across 124 languages — the usual TUI route is tree-sitter or regex grammars, so the trade-off is fidelity to VS Code's grammar behaviour versus independence from that ecosystem. Compared with Neovim, TTT trades composability and a mature plugin culture for zero-config defaults; compared with VS Code it trades extensions, debugging and a large contributor base for living in the terminal. Multi-root workspaces and opening a PR URL or piped `git diff` directly are small but practical touches.\n\n## Who it's for\n\nDevelopers already happy in a terminal who want LSP completion, a file explorer and a git staging workflow without maintaining an editor config — especially on Linux\u002FFreeBSD\u002FTermux, or over SSH where GUI editors are awkward. Look elsewhere if you depend on a deep plugin ecosystem, debugger integration, notebook-style work, or if your team standardises on VS Code extensions. Neovim users with a tuned setup will find little reason to switch.\n\n## Cost of adoption\n\nRequires Git and `ripgrep` for search; install is a single binary (Homebrew tap, AUR, scoop, Nix flake, or the install script — the flake still tracks `main`, which is a warning sign for Nix users). MIT licensed, so no constraints. The README is long on features but thin on stability guarantees, release history and performance claims; Nerd Font icons are opt-in and default off, so nothing forces a font change. The main risk is maturity: no published benchmarks and no Hacker News discussion in the signals, so real-world behaviour on large repositories is unverified.\n\n## Verdict\n\nThe project is roughly nine months old and gained 211 stars in a single week, landing at #15 on the Go weekly board without ever appearing on the daily board. That pattern — a concentrated spike, no sustained daily traction — reads as a launch moment rather than an established tool. The feature list is unusually complete for that age, and the zero-config single binary is a genuine differentiator for terminal users. But an editor is a daily-driver decision: give it a month of side-by-side use on your real repos before replacing anything.",{"slug":19,"name":20},"developer-tools","Developer Tools",[22,23,19,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40],"cli","code-editor","diff","editor","git-integration","go","golang","herdr-plugin","ide","lsp","syntax-highlighting","tcell","terminal","terminal-emulator","text","text-editor","ttt","tui","vscode-alternative","MIT","http:\u002F\u002Ftttedit.dev\u002F","2026-10-25T00:36:01Z",[],1792901787]