Ensembyte Logo
Ensembytev1.1
HydraFeaturesAgentsThemesBlogChangelogFAQ
GitHubGet Ensembyte
Ensembyte
Ensembytev1.1.5
The coding app by Soumya Chakraborty
v1.1.5 Release · MIT License
Download for macOSGitHub
$git clone https://github.com/soumyachk101/Ensembyte.git

Architecture

  • Hydra Parallel Swarm
  • Effort Reasoning Slider
  • Shadow Git Checkpoints
  • 12 CLI Agent Providers
  • 26 Liquid Glass Themes

Engineering Journal

  • Introducing Hydra
  • Why We Chose Swift
  • Git Worktree Engine
  • Zero Telemetry Audit
  • All Engineering Notes →

Downloads

  • macOS (Apple Silicon .dmg)
  • Windows 10/11 (.exe setup)
  • Linux (Universal AppImage)
  • Debian / Ubuntu (.deb)
  • Full Release Changelog

Open Source

  • GitHub Repository
  • Releases & Checksums
  • MIT License
  • Third-party Notices
  • Soumya Chakraborty (GitHub)

Explore Ensembyte

  • About
  • Features
  • Use cases
  • Compare

© 2026 Ensembyte. Built natively in Swift & Rust by Soumya Chakraborty. Free & Open Source under MIT.

MIT licensed·Built with Swift & Rust
Ensembyte
  1. Home
  2. Journal
  3. Why We Chose Swift (and Not Electron)
EngineeringEngineering6 min read

Why We Chose Swift (and Not Electron)

SC
Soumya Chakraborty
Creator of Ensembyte
September 20, 2026
Why We Chose Swift (and Not Electron)
“By rejecting Electron in favor of native Swift and SwiftUI on macOS, Ensembyte achieved an 87% lower memory footprint, instant 120fps scrolling, and zero Chromium overhead.”

When we set out to build Ensembyte, the easiest choice was Electron. Almost every modern desktop tool — VS Code, Slack, Notion, Cursor, Figma — is built using web views inside a bundled Chromium runtime. It promises cross-platform convenience at the push of a button.

The Real Cost of Chromium Wrappers

The problem is that Chromium was engineered to browse arbitrary untrusted websites, not to act as an ultra-lean desktop engine for code generation. When you open a standard Electron app, you pay a steep hardware tax: an entire V8 JavaScript runtime, a multi-process browser sandbox, and gigabytes of memory consumption.

swift
// Benchmark: Fresh Window Idle Resource Consumption
// ----------------------------------------------------
// Electron (V8 + Blink + Node.js IPC): ~320 MB baseline RAM
// Ensembyte (Swift + AppKit Metal compositor): ~42 MB baseline RAM
// Launch Time: 180ms vs 1,450ms (8.1x faster native startup)

For a developer tool managing long-running git operations, terminal buffers, and streaming AI responses, every megabyte of overhead counts. On an Apple Silicon MacBook, 40MB baseline RAM means Ensembyte stays whisper-quiet without triggering fans or draining battery.

SwiftUI and Liquid Glass Integration

Building natively with SwiftUI gave us access to Apple's Liquid Glass rendering engine for free. Instead of faking blur effects with heavy CSS backdrop-filter hacks that drop frames during window resizing, macOS handles material translucency directly on the GPU using Metal shaders.

Ensembyte running natively on macOS Sonoma with Apple Liquid Glass materials.
Ensembyte running natively on macOS Sonoma with Apple Liquid Glass materials.

The Single Dependency Philosophy

Our entire macOS Swift application has exactly one third-party library dependency: SwiftTerm, which provides the high-performance VT100 terminal emulation. Everything else — the UI components, the Git engine, the AI provider streaming parsers, and the checkpoint system — is built from scratch without bloated node_modules.

SC

Written by Soumya Chakraborty

Engineering Ensembyte — a local-first, hyper-responsive multi-agent coding workstation crafted in pure Swift and Rust.

Follow Project
Previous Essay
Introducing Hydra: One Chat, Many Heads
Next Essay
Checkpoints, Worktrees, and the Git Stack

More from the journal

Architecture

Introducing Hydra: One Chat, Many Heads

How we turned a single coding session into an autonomous swarm of parallel agents working in git worktree isolation, then landing their changes as one conflict-free merge.

8 min read
Engineering

Checkpoints, Worktrees, and the Git Stack

Every turn is a shadow git checkpoint with automatic rollback. Every thread is an isolated worktree. Here is the low-level engine behind our local concurrency.

5 min read
Design

26 Themes, One Glass Window

From Catppuccin Mocha to Tokyo Night and Dracula: designing optical contrast, tinted macOS shaders, and personal developer aesthetics.

4 min read