I appreciate your facts. But System 76 should then call it GTK based, I guess.

Only the applications are GTK-based. The compositor that makes the whole environment possible is written in Rust.

Does this work similar to the python bindings that were ubiquitous a decade ago?

My understanding is that you don't get any memory safety/performance advantage from using Rust because gtk can still be unsafe.

Is this correct?

Even Rust code can still be unsafe. It's a question of where it can be unsafe. You're reducing the scope of code that can be unsafe to specific areas.

So basically it’s not Rust.

How pure does your program have to be to be rust for you? How few libraries in C or C++ must it call? The developers are writing all their code in rust, so it is in rust…

It’s a UI library that’s showing UI controls that are written in C. It’s dishonest to call it Rust because it wraps those controls in a layer of Rust

By that standard no binary that links against glibc, whether originally written in rust or go, is in fact rust or go.