Basic native desktop UI integration on Linux (file pickers etc.), + "immediate-mode program…
@rfleury25K followers
85,586 views
48 Comments
Comments from the original post on X (Twitter)

@rfleury
This is "immediate-mode" in the sense that the user does not need to manage anything but the single bit of state that they care about ("is it installed?"). They just check a box, and everything else automatically flows from that. This is opposed to "installers" or "uninstallers", which feel like a heavyweight, "retained-mode" operation of "creating" and "destroying" an application.
108 likes

@SheriefFYI
apropos, have you seen this?
63 likes

@rfleury
Nice! I hadn’t seen this but strongly support this in general. It hasn’t taken that much extra work to ensure that raddbg.exe (or now the ELF) remains totally standalone. I wish more programs did this.
55 likes

@SheriefFYI
I think 99% of installations are just bullshit - apps should just be copyable around. I wish more people took your stance.
44 likes

@thisisdeahmed
is RADDBG now available on linux ? 😍
6 likes

@rfleury
Not yet but we're getting there
32 likes

@onceagaintoni
FilePilot does similarly I believe, in that when you run it for the first time it just asks you if you want to install it, then copies itself to the user folder and adds itself to path. But it's all the same exe
4 likes

@caballerobrah
"It is important to me that distribution of RAD Debugger binaries is as simple as possible, so I keep everything packaged as a single standalone executable." bless you
3 likes

@_rygo6
apt install rdbg pacman -S rdbg dnf install rdbg don't make me do extra steps :( This actually gets incredibly annoying if you work with hardware where you are regularly bringing up a new OS install. If it can't be one command to install it, and be ready to go, with no issue, I tend to use something else.
2 likes

@rfleury
This doesn’t make you do any extra steps. It works if you install externally too.
3 likes

@_shoen
I think this is a counter intuitive way of solving a problem that doesn’t belong within this domain. Releasing the binary and letting the community package it is probably a less invasive option. The set of requirements you are trying to fulfill from within the binary might differ from distro to distro etc
2 likes

@rfleury
This is why Linux sucks. There are no standards, and everything—like what files an application needs to integrate with the environment—is a question. This is terrible. It’s way more pragmatic & a much better user experience for the vast majority to write to the de facto standards.
41 likes

@cata_en
@_shoen xdg is not standard enough?

@rfleury
@_shoen Hence “de facto”
4 likes

@slendidev
Please tell me that this is opt-in, I would prefer for all of my .desktop files to be managed by my system's package manager. Also, how do you open the native file dialog? On Linux there's multiple variants, usually tinyfiledialogs is used for custom UIs.
2 likes

@rfleury
It is inherently opt-in; it will not do anything if you don't touch it. What do you mean by "usually"? The usual solution is to call into whatever is already installed, e.g. zenity or whatever. RADDBG already has its own file browser as a fallback.
18 likes

@slendidev
Thanks that answered my question, that's essentially what tinyfiledialogs does. Some programs decide to put a hard dependency on libraries like GTK just for file dialogs leading to inconsistencies in the UI :P
2 likes

@niknak
I don't use either of those but you are a saint for including this 🫡
2 likes

@GNUPlusRacism
Obviously that single boolean should be programs.raddbg.enable I use nixos btw
2 likes

@vulcanisma
Curious, do you use xdg portals? I went to look but it looks like you haven't commited it yet
1 like





















