Status: Early Access (Beta)

Performance Reimagined.

A zero-overhead C/C++ IDE written in pure C. No Electron. No Java. No bloat. Just speed.

Cold Boot Latency (Seconds)
Icarus0.02s
VS Code (Electron)3.40s
Visual Studio 202212.8s
Idle Memory Footprint
Icarus18MB
CLion1.2GB

Windows Toolchains

Icarus supports multiple Windows toolchains for compilation and debugging.

MSVC (Microsoft Visual C++)

Recommended for native Windows development. Debugging not supported (yet).

# Install via VS Community or Build Tools
1. Download Visual Studio Installer
2. Select "Desktop development with C++"
3. Install and enjoy

MinGW64 (via MSYS2)

Recommended for cross-platform development. Debugging fully supported.

# Install via MSYS2
pacman -S mingw-w64-x86_64-gcc
pacman -S mingw-w64-x86_64-gdb

Linux Toolchains

Native integration with standard GNU toolchains on Linux.

GCC & GDB

Standard GNU toolchain for compilation and debugging.

# Debian/Ubuntu
sudo apt install build-essential gdb

# Fedora/RHEL
sudo dnf groupinstall "Development Tools"

Binary Distributions

FREE FOR BETA TESTERS

Frequently Asked Questions

Q: The website looks "vibe-coded", have you used AI in its development or design process?

A: No, the IDE was not vibe-coded. If any AI usage was involved, it was limited to small helper tasks and parts of the website's design. Even then, the output was almost always bad and, most of the times, ended up being rewritten because it was either inefficient, overly complex, or just buggy. The Icarus codebase is engineered and mantained by a human with passion and care. I actually like manually typing code, and I find that it helps me think through problems better. I also enjoy the craftsmanship aspect of coding, and I want to maintain a high level of quality in my work. So while AI can be a useful tool for certain tasks, I prefer to rely on my own skills and not depend on it.

Q: The program has bugs and crashes often, what's going on?

A: Icarus is currently in early beta, and the open-beta test started not much time ago. So while core features are functional, lots of bugs and optimizations are still being addressed. User feedback helps guide development.

Q: Why Icarus? Why not just use VS Code, CLion, VIM, Neovim, Zed, etc.?

A: Icarus is a long-term personal project focused on simplicity and performance. You should use whatever IDE suits you best, but that doesn't mean other people can't have different preferences.

Q: Why doesn’t Icarus have feature X?

A: Development prioritizes stability and performance first. Features are added carefully rather than rushed.

Q: Why didn’t you use Electron or make it web-based?

A: Electron and web stacks are slower and less predictable. Native code allows full control over performance and memory.

Q: Is Icarus going to replace VS Code?

A: Probably not, and that’s fine. The goal is to build something enjoyable, not to compete.

Q: Is Icarus open source?

A: No. Icarus is closed source so its direction and quality can be maintained.

Q: Will you add AI code generation?

A: There is a prototype, but no plans for integration. AI code is unreliable and often inefficient.

Q: Why is Icarus written in C?

A: C is simple, fast, and gives full control over memory and performance. It’s also what I’m most proficient with.

Q: macOS support when?

A: Planned for the future, but currently limited by lack of Apple hardware for testing.