2026-07-31 · Nourish - a wayland compositor with infinite zoom and pan

Transcript

Transcript. Paraphrased; sources in notes.md.

HostWelcome to the show. It is July 31st, 2026. I am Daniel, and joining me is Victoria. We have a packed list today, starting with a new Wayland compositor called Nourish that promises infinite canvas-style interactions, then a dive into a new terminal UI for the Jujutsu version control system, and we are closing out with a look at Gossamer, a new programming language explicitly built for AI agents. Victoria, before we jump into the technical weeds, how are you holding up?

GuestI am holding up like someone who just spent three hours debugging a dependency graph that refused to resolve, Daniel. I saw the Nourish announcement pop up in my feed earlier, and my first thought was just, what is the use case here? Who is sitting at their desk thinking, I really need my entire operating system to feel like a giant whiteboard?

HostIt is a bold interface choice. Nourish, for those who need a refresher, is a Wayland compositor, which is the modern display protocol for Linux, that allows you to zoom and pan across your workspace. It uses the y5 engine and is written in Rust. It is marketed as a daily driver, but the community over on Lobsters seems a bit skeptical.

GuestSkeptical is putting it mildly. A Lobsters user called gcupc points out that while the idea has been floating around for years, the actual implementation details here are a major turn-off. And honestly, I agree. When I look at a desktop environment, I look for stability and accessibility. If I have to jump through convoluted install scripts that make me feel like I am installing a custom kernel, I am out. The author claims it is stable, but stable is a state you earn, not a label you slap on a GitHub repo. Does this actually help me ship features faster? Probably not. It sounds like an engineering vanity project that prioritizes the how over the who.

HostIt is interesting you say that, because the project also claims to collect zero telemetry and is built using AI-directed coding. David_Gerard over on Lobsters kept it brief, noting it is just vibecoded.

GuestVibecoded. I love it. Look, building a compositor is an incredible amount of work, and I respect the technical challenge. But if the primary value prop is that it is easy to navigate by zooming out, I am worried the user will spend more time navigating their desktop than actually using their applications. It is a classic case of solving a problem that does not exist for the average person trying to get work done.

HostLet us move from desktop environments to developer tools. There is a new TUI, or terminal user interface, for Jujutsu, the experimental version control system from Google engineers, called jj_tui. It focuses on snappy performance and real-time previews for rebasing.

GuestNow, this is something I can get behind. Jujutsu is great, but the command line can be intimidating. A tool that helps you visualize what your rebase will actually do before you commit to it is a genuine productivity win. It is the difference between blindly trusting your tool and actually understanding the state of your repo.

HostPeople on Lobsters are comparing it to an existing tool, jjui. A user named bahlo asked how it stacks up.

GuestAnd it sounds like it is still early days. A commenter called academician noted that it is missing some of the more advanced features, like browsing the operation logs, and, this is a funny one, the tool uses the term branches instead of bookmarks, which goes against the specific terminology choices Jujutsu made.

HostThinkChaos suggested that might be because of the LLM usage in the code, which might have a bias toward Git-centric terminology.

GuestWhich perfectly illustrates the danger of using AI to build your developer tools. If you do not have a human in the loop who deeply understands the domain, you end up leaking the design patterns of a different tool into yours. If I were the maintainer, I would care less about the AI generation and more about the user friction. If I have to keep switching mental models between the tool and the underlying system, I am just going to go back to the standard terminal commands.

HostFinally, we have to talk about Gossamer. This is a language designed specifically for AI agents, focusing on token economy and readability for models rather than humans. It uses a Swift-like memory model and Go-style concurrency.

GuestI read the spec, and the authors are very explicit about this. They want fewer keystrokes because token counts are a cost. I have to ask, who is this for? If the agent is writing the code, why do I care if it is expressive and clear syntax?

HostIt is a controversial premise. Radex over on Lobsters was skeptical, and typesanitizer pointed to the documentation where it admits the language is built for AI agents to write and edit.

GuestHere is my problem with that. We are essentially saying that human readability is now a secondary concern. But who maintains this code when the AI hallucinates? Who is going to debug an arena-allocated memory region when it goes wrong? A commenter named mempko had the best take on this in the thread. They mentioned that even if you have a world-class model like Claude, we are focusing on the wrong things. The hard part of software is not the syntax or the token count, it is understanding what to build and why.

HostIt feels like we are optimizing for the generation speed instead of the long-term maintainability.

GuestExactly. If I have to spend twice as long explaining the architecture to a language that looks like Rust but acts like Go, just so I can save a few tokens, I have lost. I would much rather use a language that is proven, readable by my team, and has a ecosystem that is not just hallucination-friendly.

HostIt has been a pleasure digging into these with you, Victoria. That is it for today. Any parting thoughts on the state of the stack?

GuestJust that I hope we stop building things for the sake of the tech and start looking at the friction points that actually keep us up at night. If your tool does not make someone's day easier, keep it in the garage. I am looking forward to a weekend of, ideally, zero terminal reconfigurations.

HostI think that is a sentiment we can all get behind. Thank you, Victoria, for joining me. All the stories today came from Lobsters, the place to be for deep tech discussions. We will be back tomorrow. See you then.