4 ms·

Why use this instead of a native window manager? GNOME, KDE, Windows, MacOS, i3 all support virtual desktops where your window layouts are preserved

by TonyStr 4mo ago

kidfiji 4mo ago
I feel that this single-pane-of-glass approach works better for some folks' mental models
- BlueBerry2001 4mo ago
  Yeah, that’s basically the mental model I’m aiming for. Not “replace the desktop”, but one pane of glass for a specific project/workflow. Some people prefer strict OS-level windows, others seem to think better when the project is laid out spatially and persists between sessions.
v3ss0n 4mo ago
agree , it should be WM isntead of a very limited electron app.
- BlueBerry2001 4mo ago
  I get that. A native WM version would be interesting, especially for performance and deeper OS integration. For now Cate is intentionally an app because it is easier to try, cross-platform, and focused on project-level workflow rather than managing the entire desktop. But I agree the boundary between spatial workspace and window manager is a real discussion.
PetitPrince 4mo ago
I conceptually agree that managing windows should be the task of... the window manager, but at the same time it's easier and lower friction to both develop inside of an app and get some user to test new features
- BlueBerry2001 4mo ago
  Exactly. I agree that the OS/window manager is the “proper” layer in theory. In practice, building it as an app makes experimentation much easier: cross-platform, lower friction to try, no need to replace your current WM, and we can iterate on workspace-specific features like terminals, browser panels, agents, Cmd+K search, worktrees, docking/tabs/splits, etc.
BlueBerry2001 4mo ago
Because native virtual desktops still mostly preserve app windows, not project context. Cate is more scoped: one workspace per project/folder with terminals, browser previews, editors, notes, agents, worktrees, docked tabs/splits, and restored panel positions. It’s not meant to replace GNOME/KDE/macOS/i3 globally, more to keep the messy project-specific layer in one persistent place.
throwthrowuknow 4mo ago
Window layout isn’t the key feature, creating a spatial map of open files and other resources is.
hnlmorg 4mo ago
That’s a fair question but I can think of one big advantage of going this way and that’s to do with distraction-free workspaces. To use a comparison, have you ever picked up your phone to enter an TOTP / one time auth code and then accidentally found yourself texting a friend, or some other non-work activity. It’s particularly easy to get distracted if you have an open notification you didn’t see until you went to use that one time code on your phone. Having a desktop app for your workspace helps hide Slack and other distracting items while context switching between different productivity apps.

Why use this instead of a native window manager? GNOME, KDE, Windows, MacOS, i3 all support virtual desktops where your window layouts are preserved

by TonyStr 4mo ago

Why use this instead of a native window manager? GNOME, KDE, Windows, MacOS, i3 all support virtual desktops where your window layouts are preserved

kidfiji 4mo ago

I feel that this single-pane-of-glass approach works better for some folks' mental models

BlueBerry2001 4mo ago
Yeah, that’s basically the mental model I’m aiming for. Not “replace the desktop”, but one pane of glass for a specific project/workflow. Some people prefer strict OS-level windows, others seem to think better when the project is laid out spatially and persists between sessions.

v3ss0n 4mo ago

agree , it should be WM isntead of a very limited electron app.

BlueBerry2001 4mo ago
I get that. A native WM version would be interesting, especially for performance and deeper OS integration. For now Cate is intentionally an app because it is easier to try, cross-platform, and focused on project-level workflow rather than managing the entire desktop. But I agree the boundary between spatial workspace and window manager is a real discussion.

PetitPrince 4mo ago

I conceptually agree that managing windows should be the task of... the window manager, but at the same time it's easier and lower friction to both develop inside of an app and get some user to test new features

BlueBerry2001 4mo ago
Exactly. I agree that the OS/window manager is the “proper” layer in theory. In practice, building it as an app makes experimentation much easier: cross-platform, lower friction to try, no need to replace your current WM, and we can iterate on workspace-specific features like terminals, browser panels, agents, Cmd+K search, worktrees, docking/tabs/splits, etc.

BlueBerry2001 4mo ago

Because native virtual desktops still mostly preserve app windows, not project context. Cate is more scoped: one workspace per project/folder with terminals, browser previews, editors, notes, agents, worktrees, docked tabs/splits, and restored panel positions. It’s not meant to replace GNOME/KDE/macOS/i3 globally, more to keep the messy project-specific layer in one persistent place.

throwthrowuknow 4mo ago

Window layout isn’t the key feature, creating a spatial map of open files and other resources is.

hnlmorg 4mo ago

That’s a fair question but I can think of one big advantage of going this way and that’s to do with distraction-free workspaces. To use a comparison, have you ever picked up your phone to enter an TOTP / one time auth code and then accidentally found yourself texting a friend, or some other non-work activity. It’s particularly easy to get distracted if you have an open notification you didn’t see until you went to use that one time code on your phone. Having a desktop app for your workspace helps hide Slack and other distracting items while context switching between different productivity apps.