HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
slint-ui
slint
Rust2020–2026
slint-ui / slint

slint

Slint is an open-source declarative GUI toolkit to build native user interfaces for Rust, C++, JavaScript, or Python apps.

27Distinct people
56Mentions
0Explicit recommenders
24.6KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Slint is an open-source declarative GUI toolkit to build native user interfaces for Rust, C++, JavaScript, or Python apps.

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

Exact – a new cross platform UI framework direct repository linkDebated

Commenters criticize the 'Exact' framework's documentation for being unintelligible and overly focused on AI agents at the expense of human developers, while others praise its innovative approach to agent-driven UI control. A secondary debate centers on whether the project is a viable cross-platform solution or an unnecessary abstraction given existing tools like Slint and Flutter.

109 readable replies · Supporting reply 1 · Supporting reply 2 · Supporting reply 3 · Supporting reply 4

Mentions over time

HN mentions by year56 dated mentions

Observed mentions: 2020-10-13 18:49:48 UTC to 2026-08-28 17:19:59 UTC.

0510152020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 3 mentions; 2 submissions, 1 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 7 mentions; 0 submissions, 7 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 16 mentions; 2 submissions, 14 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 12 mentions; 1 submissions, 11 comments20232024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 5 mentions; 1 submissions, 4 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 9 mentions; 0 submissions, 9 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC321
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC707
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC16214
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC12111
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC514
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC909
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC404

What Hacker News says

56 sources
Some notes: - The docs.rs docs are still building, but the docs from the recent RC are available [0] - The Slint project have an example of embedding Servo into Slint [1] which is good example of how to use the embedding API, and should be relatively easy to adapt to any other GUI framework which renders using wgpu. - Stylo [2] and WebRender [3] have both also been published to crates.io, and can be useful standalone (Stylo has actually been getting monthly releases for ~year but we never really publicised that). - Ongoing releases on a monthly cadance are planned [0]: https://docs.rs/servo/0.1.0-rc2/servo [1]: https://github.com/slint-ui/slint/tree/master/examples/servo [2]: https://docs.rs/stylo [3]: https://docs.rs/webrender
In Servo is now available on crates.io
I use the the code lenses of code action feature of the LSP so that the user can start a preview. The LSP server will then open a native window on desktop. Every time the users do some change in the code, the editor sends the document and we re-render the preview. I use the textDocument/documentHighlight request to know when elements are being selected from the code so I can highlight them in the preview. When selecting an element in the preview UI, my LSP server sends a window/showDocument to position the cursor at the right location. And if the user changes property or do change in the file, we do a workspace/applyEdit command with the changes. Btw, the code is there: https://github.com/slint-ui/slint/tree/master/tools/lsp
In Code-GUI bidirectional editing via LSP
Anyone considering it will need to decide for themselves how to feel about it, but I think it's important to prospective users to highlight that the current licensing model for Slint requires either GPL3-compatible licensing of your work, advertising for Slint within your own software, or paying ongoing licensing fees and/or royalties. https://github.com/slint-ui/slint/blob/master/FAQ.md#licensi... I only mention this because those constraints are notably more restrictive than the vast majority of the Rust crate ecosystem. I take no particular stance on whether this is a fair or good practice or about the technical suitability of Slint beyond this concern, I just think it's a hurdle for most people so they should be made aware early and often.
In I Switched from Flutter and Rust to Rust and Egui
I actually wrote Rust bindings for Qt a while back: https://github.com/woboq/qmetaobject-rs/. I'm curious to see how Qt's own take with Qt Bridges will work out. That said, I’ve since moved on and now work on Slint [https://github.com/slint-ui/slint] Slint was created with the same idea as what drives "Qt Bridges". We made a UI toolkit that is language-agnostic from the start. Slint uses its own UI language (inspired by QML), and gives you first-class, idiomatic APIs in Rust, C++, Pyhton, and JavaScript. And a clean separation between UI and business logic.
In Qt's New Bridging Technology – Looking Back to Move Forward
Some time ago I did research for myself on the topic of GUI libraries/frameworks. Below are some things from this study. The modern tendency for all frameworks to use 2D rendering engines to draw all widgets from scratch instead of using platforms' widgets and APIs. Usually, they use Skia. I can recommend reading blog posts by Raph Levien [1], who is one of the founders of Linebender [2] and Xilem [3]. Xilem is a Rust cross-platform GUI framework intended to use GPU for rendering in the first place. Earlier, they tried to develop their own GPU meta-API, then they switched to WGPU [4] and developed their own 2D rendering engine instead of using "standard" Skia, like many others. JetBrains develops Compose Multiplatform [5]: using the same Android API - Jetpack Compose, but for many platforms and in Kotlin. They also use Skia but are consid
Read the rest
ering switching to Impeller (a new 2D rendering engine in Flutter) because of performance issues in Skia with shaders compiling. Slint [6], was founded by 3 guys who's been working for a long time in Qt Group. It is written in Rust but uses DSL to develop GUI. As I understand, they try to solve the main fundamental issues in Qt. MAUI, as I understand it, was Xamarin.Forms and now Microsoft tries to develop it. Another interesting thing. There is a part of each GUI framework, a system to automatically place widgets on the screen - layouting, something like a grid, table, and so on. Several years ago, Apple had a big boom in the implementation and use of the Cassowary algorithm [7] in their GUI frameworks. It was a promising, strong math-based academia-proof algorithm, but in real life, as I understood, it can not work reliably in many edge cases [8], so Apple quietly removed it and implemented Flexbox [9]. More approaches: to use game engines as GUI frameworks: Unity, Unreal, Godot, etc. Fun fact: Blender has its own GUI library, which is implemented on top of OpenGL. PS If you find anything interesting, I would appreciate it if you share. PPS As a way to find more, I can recommend using search in HN, Reddit, and GitHub. Try to find projects that people develop to solve something and look at what ideas they use. [1] https://raphlinus.github.io/ [2] https://linebender.org/ [3] https://github.com/linebender/xilem [4] WebGPU implementation in Rust, used in Firefox and many other projects, can be used as a separate library, cross-platform, meta-API over Vulkan, DirectX, Metal etc [5] https://www.jetbrains.com/compose-multiplatform/ [6] https://github.com/slint-ui/slint [7] https://en.wikipedia.org/wiki/Cassowary_(software) [8] https://news.ycombinator.com/item?id=13935264 [9] https://en.wikipedia.org/wiki/CSS_Flexible_Box_Layout
In Ask HN: Modern GUI Research

Showing the 15 most recent of 56 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.