Developer Tools

Developer Tools covers the software people use to write, test, debug, and ship code. This category spans a wide range: text editors and IDEs like VS Code, Neovim, Helix, and Zed; version control systems like Git; and testing frameworks like Playwright that automate browser checks. Some of these projects are decades old and built around plugin ecosystems, while others are newer, written in Rust or Go, and designed for speed and low resource use out of the box.

When choosing between tools in this list, think about what you actually spend your day doing. If you live in a terminal, Neovim or Helix will fit better than a GUI-heavy editor. If you want something that works well without much configuration, VS Code or Zed cover more use cases out of the box, with extensions filling in the rest. For version control, Git is the default almost everywhere, so the real decision is usually about workflow and hosting, not the tool itself. For testing, look at whether the framework supports the browsers and languages your project actually uses, and how well it integrates with your CI setup.

A few practical things to check before adopting any tool here:

• Active maintenance: recent commits, responsive issue tracking, and a changelog that isn't stale.
• Extension or plugin ecosystem, if you rely on customization.
• Startup time and memory use, especially for editors used all day.
• License terms, particularly for anything you'd bundle into a commercial product.
• Community size, since it affects how easy it is to find help or existing configs.