---

Articles

Technical writing from the Vix.cpp project.

These articles explain how Vix is designed, how its major workflows operate, and why particular engineering decisions were made. They cover the runtime, CLI, build system, application manifests, diagnostics, performance, development tools, and the longer-term direction of the project.

Release notes

Follow the project’s development release by release, from the V2 runtime foundation to the latest SDK, application module, package, Cloud, and Vix Note changes.

• Vix.cpp changelog

Architecture and roadmap

These notes describe the direction of the project and the engineering work required to make native C++ applications easier to build, operate, and maintain.

• Vix.cpp roadmap
• Production simplicity checklist

Core runtime and performance

Benchmarks and implementation notes about the native runtime, lifecycle behavior, concurrency, HTTP execution, and performance validation.

• Vix Core v2.6.3 benchmark baseline

vix.app

The vix.app series explains the application manifest, how Vix resolves a project, and how it generates the build structure required by CMake and the Vix CLI.

• Why vix.app exists
• vix.app manifest design
• How vix.app generates CMake
• vix.app project resolution
• vix.app build planning
• vix.app tests and examples

vix build

A closer look at configuration, build planning, dependency loading, caching, compatibility with CMake projects, and the gradual development of the native Vix build path.

• How vix build works
• vix build and CMake compatibility
• vix build graph design
• Object caching and incremental builds
• Artifact cache design
• Toward native vix.app builds

Error diagnostics

C++ diagnostics often contain the right information in a form that is difficult to read. This series explains how Vix identifies the useful part of compiler, linker, runtime, sanitizer, and template failures.

• How Vix turns C++ errors into actionable diagnostics

vix run

These articles explain how Vix distinguishes between scripts and projects, resolves executable targets, selects the direct compiler path, falls back to CMake, and forwards runtime arguments.

• How vix run resolves targets
• vix run: script mode and project mode
• The direct C++ script runner
• vix run CMake fallback
• vix run runtime arguments

vix dev

Development workflow notes covering watch mode, rebuilds, process lifecycle, frontend integration, and full-stack projects.

• Vue frontend with a Vix C++ backend

Vix Replay

Vix Replay records previous executions so developers can inspect what ran, understand failures, and reproduce earlier runtime behavior.

• How Vix Replay works