Yue VS libui

For a recent project I chose Yue (https://libyue.com/), a cross-platform native widget GUI toolkit with C++, JavaScript/Node.js, and Lua. I've only used the Lua interface and macOS backend, but it has worked quite well, despite the very steep learning curve. This was also my first desktop GUI app, so I had to learn many implicit concepts that weren't obvious from the otherwise extensive documentation.

Yue was also the only option that 1) supported macOS, 2) supported Lua, 3) was sufficiently comprehensive to build a non-toy GUI app, 4) and that I could integrate into my (static) build. I couldn't even get the wxWidgets Lua interfaces to compile, and Qt and Fltk had similar stories, whereas reverse-engineering the baroque Yue build (based on Google's internal build systems) was relatively simple. Yue had some sharp edges, but I was able to work around them whilst patiently waiting for patches and fixes upstream.

Immediate mode interfaces were a non-starter for me. For a non-trivial set of otherwise typical controls and window management you have to implement too much yourself, plus being non-native they not only felt wrong (which admittedly is somewhat subjective; the younger crowd seems to think non-native, immediate mode interfaces look more state-of-the-art), but lacked other interfaces for proper desktop integration, like theme change signaling (i.e. notification that a user switch between light and dark modes in the macOS system settings panel).

All-in-all I would highly recommend Yue.

I settled for Yue: https://github.com/yue/yue It's been around for several years. The deciding factor for me was that is has well maintained Lua bindings as part of the core project alongside JavaScript (Node.js) and C++.

I didn't have much luck with libui (crashes, missing features, etc), and various immediate mode alternatives just require too many dependencies and other work that made integration too painful. Plus, Lua bindings for all these were always stale. In fact, Lua binding quality is pretty poor all around including for GTK, Qt, WxWidgets, and FLTK.

There are many more JavaScript developers than C++ developers.

Personally I like Yue, a cross-platform native toolkit library: https://github.com/yue/yue But much of project was already using Lua, so Node.js and Electron were never viable solutions.

A native GUI library https://github.com/yue/yue.

It was a disaster when I announced it on Hacker News, and I got numerous harassments from strangers.

But anyway 2 years since then and I'm still working on it.

You can kind of see the desktop UI train wreck in real time here.

We started with simple stable APIs for a common look and feel. For a while these were evolved and made available in other languages. This was back when native apps were consistent and intuitive and you could… uhh… actually write and ship them without bundling giant runtimes or checking a huge compatibility matrix.

Then around 2012 the train rounds the bend and screeeeech it hits some bad track and starts to derail. UI starts trying to emulate the web, a terrible UI platform, and sane compositional UI libraries and APIs are abandoned in favor of XML soup.

Since this stuff is a trash fire, this is followed by multiple incompatible attempts to replace or fix this. Most of these are abandoned dead ends.

Meanwhile the dev community just said fuck it and went to Electron, creating today’s world where a “hello world” app with an OK button is hundreds of megabytes and has to load an entire private copy of a language runtime and rendering engine.

Versions of this comedy of errors have occurred on every other platform, and of course there has been little effort to create a cross platform UI API that’s sane beyond Qt (with its own problems) and dozens of half completed OSS projects.

So enjoy Electron I guess.

There was one sane human being who tried to do this a while ago:

https://github.com/andlabs/libui

It’s the only sane desktop UI project I’ve seen in almost 20 years, an attempt to create an actual cross platform common API. But it’s abandoned of course, likely too difficult for one dev and nobody is going to provide financial support for anything that sane.

Maybe AI will get good enough some day that we can use it to do a thing like that.

What about https://github.com/andlabs/libui

Fantastic! This is similar to the C library `libui` since it also acts as a wrapper of native libraries of each platform.

If only there was a way to interface to these using some declarative minimal and highly opinionated programming language and paradigm...

https://github.com/andlabs/libui

For the GUI you will need a library or framework that interacts with your specifiv operating system and allows you to create windows and a canvas to which you can draw. You could give libui a chance.

libui-ng is a cross-platform GUI library with native widgets written in C. It is based on an earlier, (currently) inactive project known as libui. While Rust bindings for libui have existed for years (see ui-sys and iui), there is no solution for the new libui-ng; libui-ng-sys aims to fill this role.

libui

https://github.com/andlabs/libui is very nice, but unfortunately dead, if it serves your purpose consider using it, this is a fork under development https://github.com/libui-ng/libui-ng

https://github.com/andlabs/libui

Better yet, it has excellent DSLs that make it possible to build desktop apps in a way similar to HTML, but much better due to keeping all code dynamic in one language (no static/dynamic multi-language separation/mixing dissonance):

Maybe a module that uses https://github.com/andlabs/libui or a light HTML renderer?