The Orthodox File Manager Returns: Why GNOME Commander’s Rust and GTK4 Rewrite Is a Game Changer

 

GNOME Commander 2.0 rewrites the orthodox file manager in Rust & GTK4. Faster, safer, with an embedded terminal & Wayland support.

GNOME Commander 2.0 is a complete rewrite from C++ to Rust, offering memory safety, better performance, and long-term maintainability.

• The move to GTK4 brings modern theming, smoother rendering, and improved HiDPI support.

• New embedded terminal lets you run commands without leaving the file manager.

• Redesigned quick search and enhanced search dialog make finding files faster.

• Wayland support is now production-ready, addressing a major pain point for Linux users.

If you’ve ever felt frustrated dragging files between a dozen open Nautilus windows, or wished your file manager could behave more like a power tool than a pretty icon gallery, you’re not alone. 

The orthodox file manager (OFM) paradigm – twin panels, keyboard-driven navigation, and zero clutter – has been quietly solving these problems for decades. GNOME Commander, one of the few remaining OFMs on Linux, just took a massive leap forward. 

Its 2.0 release isn’t just another update; it’s a foundational rewrite in Rust and GTK4 that modernizes everything while preserving the efficient soul of tools like Norton Commander.

In this guide, you’ll learn:

• What makes an “orthodox file manager” different – and why that matters for your daily workflow.

• How Rust and GTK4 transform GNOME Commander’s reliability, speed, and future-proofing.

• The practical benefits of the 2.0’s headline features (embedded terminal, revamped search, Wayland support).

• How to adopt GNOME Commander without abandoning your existing habits.

What Is an Orthodox File Manager? (And Why You Need One)

Most file managers – think GNOME Files (Nautilus), Dolphin, or Windows Explorer – use a single-pane, spatial or list-based interface. You click into a folder, see its contents, then click back or open new windows to move things around. 

For light use, that’s fine. But when you’re wrangling hundreds of files, comparing directories, or batch-renaming media, the single-pane model becomes a straightjacket.

Orthodox file managers (also called “Commander-style” after Norton Commander) solve this with a simple, proven layout:

Two side-by-side panels – each showing a different directory. You copy or move files from the left panel to the right panel with a single keystroke (often F5 for copy, F6 for move).

• A command line (usually at the bottom) for quick shell commands.

• Keyboard-centric navigation – no mouse required for 90% of operations.

• Built-in viewers for text, hex, images, and more.

GNOME Commander has followed this tradition since its inception, but the 2.0 rewrite polishes every corner while keeping the muscle memory intact. If you’ve never used an OFM, think of it as the Vim of file managers: a steeper initial curve, but once learned, you’ll wonder how you ever lived without it.

The Two-Panel Workflow in Action

Imagine you’re organizing a photography project. You have a folder RAW/ with 500 images and a folder EXPORTS/ where you want to move the selects. In a single-pane manager, you’d open two windows, tile them manually, then drag-select and drop. In GNOME Commander:

• 1. Left panel opens RAW/, right panel opens EXPORTS/.

• 2. Press Insert (or Ctrl+T) to tag the files you want – no mouse.

• 3. Press F6 to move them. Done.

The embedded terminal (new in 2.0) lets you run exiftool or ffmpeg on tagged files without switching applications. That’s the orthodox promise: everything stays in one interface, hands on the keyboard.

Why the Rust + GTK4 Rewrite Matters (Even If You Don’t Code)

You might think, “I don’t care what language my file manager is written in – I just want it to work.” Fair enough. But the choice of Rust and GTK4 has direct, tangible consequences for your daily experience.

Rust – Memory Safety Without Speed Trade-offs

GNOME Commander’s previous C++ codebase was stable, but C++ makes it easy to introduce subtle memory bugs (use-after-free, double frees, data races). Over years, those become hard-to-reproduce crashes or security issues. 

Rust eliminates an entire class of those bugs at compile time. The result: a file manager that’s less likely to crash when you’re deep in a complex operation (like moving 10,000 files across a network mount).

Rust also brings fearless concurrency. Operations like directory scanning, thumbnail generation, and background searches can run in parallel without data races, making the interface feel snappier – especially on multi-core systems.

GTK4 – Modern Rendering and Wayland

GTK4 is not just “GTK3 with a higher number.” Key improvements:

• Hardware-accelerated rendering via a new scene graph API. Scrolling long directories and resizing panels is smoother, even on integrated graphics.

• Improved input handling – better touchpad gestures and high-precision scrolling.

• First-class Wayland support – no more XWayland fallbacks. GNOME Commander 2.0 runs natively on Wayland, which means proper fractional scaling, tear-free video previews, and better security.

For users on modern GNOME or Fedora Workstation (Wayland by default), this is a huge quality-of-life upgrade. Previous versions had flickering issues or misbehaving drag-and-drop on Wayland; those are largely gone.

Long-Term Maintainability

Open-source projects live or die by contributor interest. A modern Rust+GTK4 codebase is far more attractive to new developers than a C++ codebase using older GNOME libraries. 

That means GNOME Commander 2.0 is more likely to receive bug fixes and new features five years from now. That’s the essence of evergreen content – choosing tools with a future.

Breaking Down GNOME Commander 2.0’s New Features

Beyond the rewrite, the 2.0 release introduces several practical improvements that directly affect how you work.

Embedded Terminal (No More Alt+Tabbing)

You can now open a terminal inside the active panel (toggle with F12 or a toolbar button). This terminal is linked to the current directory – if you change panels or folders, the terminal follows. Run git status, grep, rsync, or even vim on a file. The output stays visible while you continue navigating.

Real-world use case: You’re cleaning up a server’s log directory. In the left panel, you see error.log. Instead of opening a separate terminal emulator, typing cd /var/log, then tail -f error.log, you just focus the left panel, press F12, and run tail -f error.log. All without leaving GNOME Commander.

Redesigned Quick Search

Press Ctrl+S and start typing – GNOME Commander now highlights matches in real time, with a subtle progress bar for large directories. The old version used a modal dialog that interrupted your flow. Now it’s non-modal, so you can refine your search while still interacting with files.

Search Dialog Enhancements

The advanced search (Alt+F7) now supports:

Content search with regex (PCRE2) – find that one config line buried in 1000 text files.

Search in subdirectories with a recursion depth limit (great for deep trees).

Save/load search profiles – “recently modified PDFs” or “large video files” as reusable templates.

Internal Viewer & Keyboard Shortcuts Dialog

The built-in file viewer (press F3) now handles larger files more efficiently and has better UTF-8 detection for log files. The keyboard shortcuts dialog (Ctrl+F1) is fully searchable – type “rename” and see that F2 is the key. That’s a small but welcome change for new users learning the orthodox workflow.

Accessibility & Wayland Improvements

GNOME Commander 2.0 passes more accessibility tests (screen readers like Orca now announce panel changes correctly). Wayland support includes proper drag-and-drop between the file manager and other Wayland-native apps (e.g., dragging a photo from GNOME Commander into GIMP).

Common Mistakes to Avoid When Switching to an Orthodox File Manager

Even with all these improvements, GNOME Commander has a learning curve. Avoid these pitfalls:

Reaching for the mouse constantly. The power is in the keyboard. Force yourself to use Tab to switch panels, Enter to open, Backspace to go up a directory, and function keys for copy/move. Within a week, it becomes second nature.

Ignoring the command line. The bottom bar (activate with Ctrl+Enter or just start typing) accepts shell commands. You can run ls -l, mkdir newfolder, or even ./script.sh. This saves you from opening a terminal for trivial tasks.

Not using file tagging. In single-pane managers, you select a group of files once, then lose the selection if you click elsewhere. GNOME Commander’s tagging (Insert key) persists as you navigate – you can tag files across multiple directories, then copy/move them all at once.

Assuming it’s only for advanced users. The 2.0 release added a “simple mode” (View → Simple Interface) that hides the command line and function key hints for beginners. Start there, then graduate to full mode.

Frequently Asked Questions

Q: Is GNOME Commander a replacement for Nautilus (GNOME Files)?

A: Not exactly. Nautilus integrates with the GNOME desktop (trash, network shares, GVfs). GNOME Commander is a complementary power tool. You can set it as your default file manager, but some desktop integration (like desktop icons) may not work. Most users keep both: Nautilus for quick access and seamless GNOME integration, GNOME Commander for heavy lifting.

Q: Does the Rust rewrite mean better performance?

A: Yes, especially for operations on directories with thousands of files. The new asynchronous scanning (thanks to Rust’s async/await) keeps the UI responsive while thumbnails load. That said, the biggest gains are in stability and memory safety – you’ll notice fewer mysterious crashes, not necessarily a 10x speedup.

Q: Can I use GNOME Commander on other desktops (KDE, XFCE, etc.)?

A: Absolutely. It only requires GTK4 libraries, which are available on any Linux distribution. On KDE, it will use the GTK theme you have set. The Wayland improvements also benefit Plasma’s Wayland session.

Q: How do I install GNOME Commander 2.0?

A: Check your distribution’s repositories. As of this writing, it may be in unstable/backports. Otherwise, you can build from source via the GitHub repository (the README has detailed instructions). Flatpak is also planned – watch the project’s releases.

Actionable Conclusion – Your Next Steps

GNOME Commander 2.0 isn’t just a nostalgia trip for greybeards who remember Norton Commander on DOS. It’s a modern, safe, and efficient file manager that solves real problems: moving files between deep directories, batch operations, and keeping your hands on the keyboard. 

The Rust+GTK4 rewrite ensures it will remain relevant for years, and the 2.0 features (embedded terminal, faster search, Wayland) close the gaps that kept some users away.

Here’s your one clear next step:

Install GNOME Commander 2.0 today. If it’s not in your repos, build from source or grab the Flatpak (when available). Then commit to using it for one specific task every day for a week – for example, organizing your Downloads folder or backing up photos. Force yourself to use keyboard shortcuts. By day five, you’ll feel the efficiency gains.