Skip to main content

Why Monolex is Stable

Monolex is built differently from other terminals. Here’s why it feels so much more stable.

The Three Pillars of Speed


Pillar 1: Native Speed (Alacritty VTE Parser)

Most terminals use JavaScript to understand terminal commands. Monolex uses the Alacritty VTE Parser - the same battle-tested Rust parser used by the popular Alacritty terminal.
Think of it this way: JavaScript is like giving directions through a translator. Rust is like speaking the computer’s native language directly.

Pillar 2: Smart Updates

Monolex only sends what changed, not the entire screen:

Data Reduction Visualization (Stage 2: True Partial Mode)

Automatic Mode Selection (The 50% Rule)

Monolex automatically picks the fastest method based on how much changed:
When you run commands like clear or scroll through long output, Monolex switches to FULL mode automatically. For normal typing and editing, it uses PARTIAL mode. You don’t need to configure anything.

How It Works: Hash-Based Diffing

Instead of comparing every character, Monolex uses fingerprints (hashes) to instantly detect changes:
Why is this faster? Traditional terminals compare 4,800+ characters per frame. Monolex compares just 40 fingerprints - 120× faster comparison.

Real-World Examples


Pillar 3: Direct Display

Other terminals process data multiple times. Monolex does it once:

Real Impact

CPU Usage

Smoothness


The Complete Picture


Comparison Summary


Summary

All of this happens automatically. You don’t need to configure anything. Just use Monolex and enjoy the speed!

Next Steps

Smooth Rendering

Learn how Monolex eliminates flicker completely.

Troubleshooting

Having issues? Check our troubleshooting guide.

Technical Deep Dive

Want to understand the implementation details? Check out these technical pages:

Atomic Loop

How MonoTerm detects frame boundaries using cursor patterns and BSU/ESU markers.

BSU/ESU Protocol

The explicit frame synchronization protocol (Mode 2026) that enables perfect rendering.