Commander 2.0 gives an old Linux workflow a modern foundation
GNOME Commander 2.0 modernizes a dual-pane Linux file manager without abandoning its original workflow.📷 AI-generated image / TECH&SPACE
- ★GNOME Commander 2.0 has been rewritten in Rust and now uses the GTK4 toolkit.
- ★The application keeps the orthodox file manager approach inspired by Norton Commander.
- ★The change matters for Linux desktop maintainability, even without broad market or AI relevance.
That is not a cosmetic update. GNOME Commander belongs to the class of file managers built around a two-pane, keyboard-driven workflow: one file tree on the left, another on the right, with fast copying, moving and comparison operations at the center. The model is old, but still useful for people who treat the file system as a working surface rather than a gallery of icons.
The Rust move therefore carries real technical weight. Across FOSS projects, Rust is increasingly used where maintaining older C or C++ code becomes expensive, especially when memory safety and long-term readability matter. The supplied context does not support claims about dramatic new features, benchmarks or a changed product strategy. The more grounded point is stronger: a long-running tool has received a modern foundation.
The Norton Commander model has survived another generation: GNOME Commander 2.0 has been rewritten in Rust and moved to GTK4.
The dual-pane file manager remains the center of the story while Rust and GTK4 reshape the base underneath.📷 AI-generated image / TECH&SPACE
GTK4 is the second half of the reset. GNOME applications that stay tied to older UI layers become harder to maintain, integrate and package over time. Moving to GTK4 brings GNOME Commander closer to the current GNOME desktop stack without forcing it to abandon its orthodox file manager identity. Ideally, the user still gets the same work logic, while the technical layer underneath is made more current.
For a broad audience, this is not a headline on the scale of a new operating system or a major commercial product. For the Linux desktop ecosystem, it has a different value: it shows that niche tools with a long tail of users can survive when technical debt is actively handled instead of endlessly patched. GNOME Commander is not the central GNOME file manager; it serves a different kind of user and a different style of work.
In that sense, GNOME Commander 2.0 is a small but clean signal. The FOSS desktop does not live only on new interfaces and platform announcements. It also depends on maintaining tools that are useful enough for someone to rewrite rather than let them disappear. More project context is available from the GNOME Commander site, while development is tied to the broader GNOME ecosystem and public repositories such as GNOME GitLab.
