Pragtical: Practical and pragmatic code editor

Original Article ↗ Hacker News Discussion ↗

Origins and Goals

  • Pragtical is a fork of Lite XL, itself a fork of Lite; it uses SDL and Lua.
  • Project motivation includes countering the trend of web-stack/Electron-based editors and staying small, fast, and local/CLI-driven.
  • Some see it as philosophically similar to Atom (almost everything is a plugin) but shipped with fewer default plugins and more focus on lightness.

UI, Scaling, and Rendering

  • Several users report extremely tiny, misaligned UI on 4K and Retina displays (especially on Windows and macOS); scaling and font settings sometimes help, sometimes do nothing.
  • On some Linux setups (e.g., Ubuntu 4K) it looks fine; on GNOME with fractional scaling via an experimental feature, SDL-based rendering appears blurry.
  • The UI reminds some of Godot; rendering is discussed as blitting glyph buffers via SDL, with some confusion over “immediate mode.”

Plugins, Extensibility, and Lua

  • Lua as extension/config language is widely praised: simple, productive, and comparable to NeoVim, WezTerm, Hammerspoon, etc.
  • Users like that almost everything can be extended or overridden at runtime (e.g., via init.lua), inspired by Emacs-style live evolution.
  • Criticism: many very small “atomic” plugins are needed (indent, matching brackets, markers, build, settings page, etc.) just to reach basic editor/IDE comfort; some wish more shipped by default.
  • The in-editor plugin browser can hang and mixes plugins, themes, and fonts, making discovery harder.
  • No LLM/AI plugins are known yet; one user asks about custom drawing/diagram modes without clear follow-up.

Performance, Footprint, and Bloat

  • Binary is ~3–5 MB; runtime memory around 30 MB is considered excellent by some, irrelevant by others unless an app becomes a “memory hog.”
  • Discussion broadens to tool bloat: VS Code devcontainers and many extensions can push startup to minutes and memory near 1 GB; some see lightweight editors plus LSP as a relief.

Installation and Stability

  • Multiple macOS users get “app is damaged” errors, attributed to code-signing/quarantine; workarounds include xattr and right-click–open, though macOS Sequoia tightens this.
  • Some report crashes when opening simple files and overall immaturity; others find it fast and stable but too barebones.

AI-First vs Core-First Editors

  • Some argue any non–AI-first IDE will struggle as tools like Cursor gain traction.
  • Others strongly prefer a solid, pluggable core where AI remains an optional extension rather than a defining feature.