Blender's UI and Runtime: Much Faster Than GPUI

A new project extracts Blender’s fast, GPU-optional interface code into a standalone GPL-licensed UI library usable from languages like Python, Rust, and JavaScript, prompting interest from developers frustrated with existing toolkits such as GPUI, egui, and Tkinter. Commenters debate whether Blender’s dense, power‑user‑oriented GUI is a good general model, contrasting it with tools like Inkscape, GIMP, Qt, and native OS widgets, and highlighting trade-offs between performance, familiarity, and platform integration. Many see the main barriers to adoption as the GPL license, lack of accessibility support, and the fact that much of the code and documentation were generated by LLMs, raising concerns about long‑term maintenance and fidelity to Blender’s behavior.

Project overview & goals

  • BUI extracts Blender’s UI system into a standalone library usable from multiple languages (Python, Rust, JS/React/Svelte, C/C++, Dear ImGui).
  • Intended for dense, performance‑sensitive “prosumer” tools (3D, video editors, DAWs, simulation, game editors) rather than simple CRUD apps.
  • GPU rendering is optional; default is CPU. GPU backends use D3D11 on Windows and OpenGL 3.3 on Linux. macOS GPU story is unclear.

Performance and capabilities

  • Many commenters see value in reusing Blender’s highly optimized widgets, especially numeric controls, pane splitters, and dense layouts.
  • BUI can run without a modern GPU, contrasting with complaints that GPUI requires one and is unusable in some contexts.
  • One commenter notes BUI’s web demos initially lacked several hallmark Blender behaviors (multi‑field drag edit, keyboard shortcuts, etc.), arguing it behaves more like a styled immediate‑mode UI; project author says web demos were mockups and later updated.
  • Questions about long‑term syncing with Blender’s evolving UI remain open.

Licensing & adoption

  • Code is derived from Blender’s GPL, so BUI is GPL (effectively GPLv3 only in practice), not LGPL.
  • Many view this as a dealbreaker for use as a general‑purpose UI library, since applications must also be GPL.
  • Others defend GPL as central to Blender’s survival and see “contribute back or stay away” as a feature, not a bug.
  • Some find the “GPLv2 or later” badge wording misleading given the effective constraints.

Blender UI as a model

  • Opinions on Blender’s UI are sharply divided:
    • Fans praise its speed, consistency, customizability (pane splitting, workflows), and polish compared to other FOSS graphics apps.
    • Critics find it unintuitive or “awful,” sometimes preferring UIs from other 3D tools (e.g., Modo, ZBrush, Softimage) and warning against spreading it beyond Blender.
  • Several stress that these tools are inherently complex, so no 3D UI feels truly “intuitive”; what feels natural often reflects familiarity.

LLM‑generated code and documentation

  • The repository and README are explicitly LLM‑generated, largely by stripping non‑UI code from Blender.
  • Some see this as a win (no human would invest that effort; easy to fork or redo with more tokens).
  • Others worry about “vibe‑coded slop,” missing fine behaviors, long‑term maintenance, and security review.
  • The README’s LLM style divides opinion: some praise its clarity and screenshots; others experience “LLM nausea” and distrust it.

Accessibility, native integration, and “native vs custom” debate

  • BUI currently has no accessibility support and does not integrate with platform a11y APIs; docs warn against using it where accessibility is required, though it’s “planned.”
  • It does not match system themes or fonts yet; some people want this, others argue that desktop UIs are already visually fragmented and native toolkits often fail at dense, custom UIs.
  • There is recurring tension between recommendations to “use native widgets” and the reality that cross‑platform, GPU‑integrated, high‑density UIs often diverge from native toolkits.

Comparisons with other toolkits & Rust ecosystem

  • GPUI vs others: conflicting anecdotal claims about speed; one benchmark suggests GPUI can be slower than Dioxus, Iced, egui, and Slint on some CPU‑bound operations, but methodology is acknowledged as rough.
  • Some feel GPUI is overhyped, single‑purpose, and constrained by needing modern GPUs; others still consider it among the more interesting Rust UIs.
  • BUI is contrasted with egui/immediate‑mode UIs, Qt/GTK, Tkinter (derided as ugly/retro), and web‑based approaches; several say BUI would have been attractive if they hadn’t already invested in their own GPU GUIs.