Prefer building TUIs (Text User Interfaces) over GUIs (Graphical User Interfaces) because:
1. Principle of Least Power says so
2. There is a smaller attack surface for supply-chain attacks
3. There is a smaller attack surface at runtime
@babble_endanger actually, prefer CLIs
they’re more accessible >:3
(but TUIs are also great! TUIs also take way less resources and dependencies…they do suck for accessibility tho, particularly if you update the screen rapidly, especially if updating whole screen)
@babble_endanger
Would argue that TUIs are just a weird GUI toolkit with a bunch of historical limitations and accessibility issues.
@babble_endanger GUIs are a lot more friendly for new users. Depends on a lot of stuff but I’d usually say have both if possible
@aens If I ever get my ass back into GUI stuff I would love to explore:
1. Common system that can present as either a TUI in a terminal or a GUI with basic animations and mouseover stuff to be friendly
2. TUI that follows system theming so it looks like a good Windows 95 GUI (e.g. grey 3D buttons on grey background, black text)
@6 TRUE
ofc on Windows with its silly subsystem thing, CLI + TUI in a single binary is easier than CLI + GUI in a single bnary
@babble_endanger
make a cli + optionally RPC (for speed, no constant proccess spawning overhead)
and then tui, or gui, plugs into it, separately >:3
@babble_endanger
That being said it's been years since I've made a desktop GUI app because all the toolkits seem kind of weird and bad
@petty_webmistress Yeah they really are. Here's my view...
1. GTK - C-first and recently went through one (or two?) major version bumps, so hard to support old OSes
2. Qt - C++ and Python-first, corporate, requires a CLA, DLL hell to distribute, hard to support old OSes
3. Tauri - Actually not half bad. But since it depends on gtk WebKit, hard to support old OSes
4. Electron - Well it's Electron, you're gonna struggle to get under 80 MB releases
🧵
@petty_webmistress
5. WinUI - lol lol lol
6. C# WPF / XAML - Absolutely slam dunk grand slam hole in one, if you are supporting Windows 10/11 and ONLY Windows 10/11
7. iced / egui / slint / whatever Rust things - Can't keep track of 'em. Some are okay some aren't
8. imgui - I can't get over the name but it seems popular among gamedevs
FLTK was actually really good last time I touched it. I used it from Rust. It was missing like one feature my company needed, but for a personal project it was good.
But it's still C++.
xkcd 927 be damned, Linux needs one more GUI framework.
It needs to be memory-safe, it needs to use existing well-known paradigms, and it needs a plan to ship small static binaries on 5-year-old Ubuntus
@babble_endanger @petty_webmistress
https://github.com/webview/webview is cool, but like tauri, uses gtk webkit…
there’s also FOX toolkit! you like windows 95? too bad! that’s what you’re getting! http://fox-toolkit.org/ it doesn’t say it’s mac-compatible, but it supports basically anything else, like solaris, AIX, IRIX, and windows 2000, lol
tcl/tk is a thhing too lol
wikipedia claims that supports even android huh
wxwidgets is a thing!
prolly more but I’m lazy and eepy
they're more accessible >:3
I'd say that's more a result of the complete lack of care for accessibility in computer systems for the longest time than a true fundamental part of it.
CLIs that aren't designed for accessibility often aren't exactly very friendly as either audio or braille output.