I think this is pretty common on Linux. You would want to GTK (or Qt) I would think to draw the top level window and perhaps system menus, etc. even though the UI itself is drawn using a GPU canvas.

> You would want to GTK (or Qt) I would think to draw the top level window and perhaps system menus, etc. even though the UI itself is drawn using a GPU canvas.

No, you would want to draw for Wayland or X. GTK and Qt themselves don't burden with importing each-other to work, for example.

My guess is that they import GTK only to get a title bar on GNOME, as GNOME forces applications to render their own. They could go custom and cut the dependency but it never looks quite right when apps do that.

No. On Wayland all of that should be in the compositor. Window sizing and positioning can not be done by the apps, so it makes sense that the controls for that are drawn and handled by the WM. But Gnomes gotta gnome...

Are GTK/Qt memory safe now?

No. What is the likelihood of an attack on a desktop program via memory unsafety?

Really high?

What do you run your browser as?

Browser runs complex untrusted code from the internet. Most desktop programs don't do anything like that. The servo programmers were riding a motorbike. Using Rust for a desktop program would be more like wearing a crash helmet in a car.

>What is the likelihood of an attack on a desktop program via memory unsafety?

Low.

What's the likelihood of someone entering your house if it's unlocked?

Also low, and yet you lock it.

A desktop program is already in a locked house - your desktop - which I can't login to.

[flagged]

Do all desktop programs only ever run in "your house"?