areweguiyet VS nodegui

The organization behind QT (QT Group) has pretty onerous licensing terms.

My understanding is that it's $3,950 per year just to develop using their libraries on your own computer if you ever in the future intend to commercialize a product using QT. Transitioning from the open source license to the commercial license is something you can do but it's not the happy path and their FAQ seems to indicate that it comes with some sort of penalty.

https://www.qt.io/pricing

Something like Slint (Rust based but includes CPP and JS bindings) is not as comprehensive (yet) but it's more modern and the licensing terms are significantly more in line with software industry norms.

GPUI from Zed is also something to monitor: https://www.gpui.rs/

Also, in general you can find an extensive list of Rust-based native UI libraries here: https://areweguiyet.com/

I would suggest that nearly every person on this website is a developer. Both C and C++ let you shoot yourself in the foot quite easily, but at least C++ has RAII.

If you're referring to Rust, it's just not there yet for anything serious: https://areweguiyet.com/

I normally use python to do some quick data analysis, with pandas/polars/pyspark/...

But I've started to use rust more and more in the last few weeks and really start to like it.

Does anyone have experience doing data analysis with rust, and would you recommend it over python?

And are there any resources like https://areweguiyet.com/ but for data analysis?

You still haven't said anything about why those existing frameworks don't count. Again, they are used in production and do exactly what a gui framework is supposed to do. Sure they may not have all the features of the frameworks that have existed a decade before rust even existed but the issue is time not rust itself. They very clearly can be used to build complex UI without inheritance. Since you mentioned it, you should probably actually look at it https://areweguiyet.com/ the page clearly says that GUI frameworks do exist in rust.

The web site https://areweguiyet.com/ has a list of GUI libraries for Rust.

I haven’t tried any yet as I lack the time, but it can be a good starting point.

Iced and Slint where interesting when I looked at that, and Slint may be done by former Qt developers.

I also hope that it is consistent with the goals mentioned at https://areweguiyet.com/

This looks like it hasn't been maintained in years but there's a modern equivalent in NodeGUI [1] which also has React/Svelte/Vue implementations. Unfortunately it requires a custom build of Node that merges the libuv and Qt6 event loops so YMMV.

It actually inspired me to write my own implementation with Svelte on top of QuickJS and Qt Widgets but the task of wrapping the entire Qt6 API in Rust proved to be intractable once I found out that most methods weren't marked Q_INVOKABLE and thus couldn't be called via reflection (requiring manual wrapping). Providing a `Document.createElement` API that created Qt Widgets with working attributes and event handling worked surprisingly well though!

[1] https://github.com/nodegui/nodegui

Hi, so this NodeGui library for building apps with native components is something I really want to get into, but, it does not work for me.. so I am starting this thread to check with yous (I depleted google results) if any one of you have tips or workarounds I can use. I wish to build a desktop app, but I really do not want to bundle a web browser for that purpose and NodeGui seems perfect.

Use NodeGui (or some equivalent tool) for this. Source: https://docs.nodegui.org/ This is needed because this entire project will run natively, by that I mean it will run with no browser, no local host and it no internet connection.

NodeGUI

Let's continue exploring Electron alternatives. This time, NodeGui. NodeGui uses Qt5 instead of Chromium, so we'll be leaving the familiar web development behind, but it tries to not be too far from it, as web development is what everyone knows.

(Disclaimer: My knowledge of Rust very limited, but I have quite a bit of experience with getting Qt/KDE classes to work with other languages.)

You are absolutely right. The effort to be acceptable bindings for Qt would be a tiny fraction of the cost compared to building a whole new Rust native GUI library.

Qt is huge set of libraries with an equally huge API. But there are a lot of shortcuts and smart ways of approaching the problem to get what you want out of Qt for minimum effort.

Bindings like PyQt and even PySide go for the nuclear option of generating bindings for the whole Qt API and trying to match the C++ API in style too. This is an absolutely massive huge task. Also, getting people to contribute to an open source bindings project is hard. Getting people to contribute to a bindings generator is even harder.

NodeGui https://github.com/nodegui/nodegui, Qt bindings for Nodejs, on the other hand takes a very different approach which in one way is low-tech but I think is actually very smart. I'll summerise the differences:

* It focuses on Qt Widgets first. This greatly reduces the amount of work to the parts that people actually need. (BTW, if you just want QML and Rust back-end then Jos van den Oever's work at https://invent.kde.org/sdk/rust-qt-binding-generator has probably got you covered already.)

There is actually a new GUI framework based out of Qt (a C++ GUI framework) that I have found recently : https://docs.nodegui.org/