Zed is Ready For Primetime 🔗 **Source:** [Zed is Ready For Primetime](https://www.youtube.com/watch?v=bRK3PeVFfVE) > [!note]+ Document Notes > tags: [Zed, Code Editor, Developer Tools] > author: [MISSING] > source: [YouTube] > reference: [https://www.youtube.com/watch?v=bRK3PeVFfVE] > date created: > > # 🏷️ Title: Zed is Ready For Primetime > <!-- deep-read:sections start --> ## 🧰 Action Inbox - [H1] Publish “Why Zed now” primer — video context at 05:32. [YouTube](https://www.youtube.com/watch?v=bRK3PeVFfVE&t=332) #articleseed - [H3] Create Zed vs VS Code UX table — themes, panels, problems. [YouTube](https://www.youtube.com/watch?v=bRK3PeVFfVE&t=1560) #xref - [H6] Write Zed Git UI quickstart — staging, hunks, diffs. [YouTube](https://www.youtube.com/watch?v=bRK3PeVFfVE&t=1140) #articleseed - [H8] Draft “Language servers dashboard” guide — restart and status. [YouTube](https://www.youtube.com/watch?v=bRK3PeVFfVE&t=1950) #xref - [H10] Document “Shift+Esc focus mode” — reduce distractions. [YouTube](https://www.youtube.com/watch?v=bRK3PeVFfVE&t=1813) #share - [H11] Outline Zed AI setup paths — Copilot and Zed provider. [YouTube](https://www.youtube.com/watch?v=bRK3PeVFfVE&t=2399) #articleseed - [H12] Propose OSPO eval rubric for editors — performance, ecosystem, AI. #addendum - [H9] Build “Split-and-move pane” cheat sheet — keybinding and workflow. [YouTube](https://www.youtube.com/watch?v=bRK3PeVFfVE&t=2356) #share ## 🧭 Table of Contents - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#️-notes) - [📚 References](#-references) - [🗣️ Paraphrase](#️-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [📊 Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB Assessment](#-deib-assessment) - [✅ Logical Validity](#-logical-validity) - [🛡️ DARVO Analysis](#-darvo-analysis) - [🎯 Conclusion](#-conclusion) ### 🔗 References - Include links cited in or relevant to the article. ## 📝 Summary - The hosts assess Zed, a Rust-based editor. - They report strong performance and thoughtful UX. - They compare Zed with VS Code and Cursor. - They note a smaller extension ecosystem and tradeoffs. - Bottom line: Zed feels fast and production ready. ## 📖 Main Content - Zed aims for speed and cohesive design. - It ships a clean UI and sensible defaults. - The marketplace exists but remains thinner than VS Code. - Git integration now covers staging and diffs well. - The problems panel feels clearer than VS Code’s panel. - Collaboration supports shared sessions with voice chat. - AI features integrate with Copilot or Zed’s provider. - Language server status is visible and controllable. - Zed supports flexible pane management and focus mode. - The talk claims “ready for prime time” with caveats. **Context sources:** - Video transcript and summary. [YouTube](https://www.youtube.com/watch?v=bRK3PeVFfVE) - Zed product site and docs. [zed.dev](https://zed.dev) - VS Code docs. [code.visualstudio.com](https://code.visualstudio.com/docs) - Tree-sitter overview. [tree-sitter.github.io](https://tree-sitter.github.io/tree-sitter/) ### 🗒️ Notes #### ⏱️ [00:27](https://www.youtube.com/watch?v=bRK3PeVFfVE&t=27) Episode scope ### [H1] Hosts evaluate Zed’s readiness today > [!quote] [Zed is Ready For Primetime](https://www.youtube.com/watch?v=bRK3PeVFfVE) by an unnamed author via [[YouTube]]. Published [MISSING]. Accessed . > “Today we’re going to be talking about zed.” Sets scope for a readiness review. [view highlight](https://www.youtube.com/watch?v=bRK3PeVFfVE&t=87) #articleseed ID:rw_[MISSING] #### ⏱️ [05:32](https://www.youtube.com/watch?v=bRK3PeVFfVE&t=332) Return to Zed ### [H2] Pain points from earlier builds are fixed > [!quote] [Zed is Ready For Primetime](https://www.youtube.com/watch?v=bRK3PeVFfVE) > “All of my annoyances had been totally fixed.” Signals maturity across prior gaps. [view highlight](https://www.youtube.com/watch?v=bRK3PeVFfVE&t=332) #xref ID:rw_[MISSING] #### ⏱️ [06:38](https://www.youtube.com/watch?v=bRK3PeVFfVE&t=398) Design first ### [H3] UI quality and themes impress out-of-box > [!quote] [Zed is Ready For Primetime](https://www.youtube.com/watch?v=bRK3PeVFfVE) > “The UI looks awesome out of the box.” Design polish reduces setup time. [view highlight](https://www.youtube.com/watch?v=bRK3PeVFfVE&t=398) #articleseed ID:rw_[MISSING] #### ⏱️ [11:46](https://www.youtube.com/watch?v=bRK3PeVFfVE&t=706) Marketplace reality ### [H4] Zed marketplace remains less rich than VS Code > [!quote] [Zed is Ready For Primetime](https://www.youtube.com/watch?v=bRK3PeVFfVE) > “The extension marketplace… is not as rich as VS Code.” Expect fewer plugins and workarounds. [view highlight](https://www.youtube.com/watch?v=bRK3PeVFfVE&t=706) #xref ID:rw_[MISSING] #### ⏱️ [14:13](https://www.youtube.com/watch?v=bRK3PeVFfVE&t=853) Authoring tradeoff ### [H5] Rust-based extensions raise entry barrier > [!quote] [Zed is Ready For Primetime](https://www.youtube.com/watch?v=bRK3PeVFfVE) > “If the extensions must be written in Rust… not every idiot like me can… quickly.” Powerful, but fewer casual authors. [view highlight](https://www.youtube.com/watch?v=bRK3PeVFfVE&t=853) #articleseed ID:rw_[MISSING] #### ⏱️ [17:54](https://www.youtube.com/watch?v=bRK3PeVFfVE&t=1074) Git workflow ### [H6] Git UI lands solid staging and diffs > [!quote] [Zed is Ready For Primetime](https://www.youtube.com/watch?v=bRK3PeVFfVE) > “The Git UI… rips.” Crucial feature now meets expectations. [view highlight](https://www.youtube.com/watch?v=bRK3PeVFfVE&t=1074) #xref ID:rw_[MISSING] #### ⏱️ [22:59](https://www.youtube.com/watch?v=bRK3PeVFfVE&t=1379) Problems view ### [H7] Problems panel improves triage clarity > [!quote] [Zed is Ready For Primetime](https://www.youtube.com/watch?v=bRK3PeVFfVE) > “This is a great little ‘knock out problems’ list.” Faster lint and type fix cycles. [view highlight](https://www.youtube.com/watch?v=bRK3PeVFfVE&t=1379) #xref ID:rw_[MISSING] #### ⏱️ [27:00](https://www.youtube.com/watch?v=bRK3PeVFfVE&t=1620) Collab pitch ### [H8] Built-in collaboration includes voice chat > [!quote] [Zed is Ready For Primetime](https://www.youtube.com/watch?v=bRK3PeVFfVE) > “You can invite someone… and then they can get voice chat.” Useful for pairing and reviews. [view highlight](https://www.youtube.com/watch?v=bRK3PeVFfVE&t=1620) #share ID:rw_[MISSING] #### ⏱️ [32:59](https://www.youtube.com/watch?v=bRK3PeVFfVE&t=1979) LSP awareness ### [H9] Language servers show status and controls > [!quote] [Zed is Ready For Primetime](https://www.youtube.com/watch?v=bRK3PeVFfVE) > “It shows you every… language server… running.” Operational clarity aids debugging. [view highlight](https://www.youtube.com/watch?v=bRK3PeVFfVE&t=1979) #xref ID:rw_[MISSING] #### ⏱️ [38:58](https://www.youtube.com/watch?v=bRK3PeVFfVE&t=2338) Pane management ### [H10] Split-and-move pane improves multitasking > [!quote] [Zed is Ready For Primetime](https://www.youtube.com/watch?v=bRK3PeVFfVE) > “Move item to pane in direction.” One command shows two files side-by-side. [view highlight](https://www.youtube.com/watch?v=bRK3PeVFfVE&t=2338) #articleseed ID:rw_[MISSING] #### ⏱️ [30:13](https://www.youtube.com/watch?v=bRK3PeVFfVE&t=1813) Focus mode ### [H11] Shift+Esc toggles distraction-free view > [!quote] [Zed is Ready For Primetime](https://www.youtube.com/watch?v=bRK3PeVFfVE) > “Shift escape… makes it full screen.” Quick focus without closing panels. [view highlight](https://www.youtube.com/watch?v=bRK3PeVFfVE&t=1813) #share ID:rw_[MISSING] #### ⏱️ [39:59](https://www.youtube.com/watch?v=bRK3PeVFfVE&t=2399) AI plumbing ### [H12] AI works with Copilot or Zed models > [!quote] [Zed is Ready For Primetime](https://www.youtube.com/watch?v=bRK3PeVFfVE) > “You can use any of the Copilot models… or use Zed.” Flexible provider choices reduce lock-in. [view highlight](https://www.youtube.com/watch?v=bRK3PeVFfVE&t=2399) #articleseed ID:rw_[MISSING] ## 📚 References - Video episode: Zed is Ready For Primetime. [YouTube](https://www.youtube.com/watch?v=bRK3PeVFfVE) - Zed product overview. [zed.dev](https://zed.dev) - Zed extensions and language servers. [zed.dev/docs/extensions](https://zed.dev/docs/extensions) - VS Code Docs. [code.visualstudio.com/docs](https://code.visualstudio.com/docs) - Tree-sitter project. [tree-sitter.github.io](https://tree-sitter.github.io/tree-sitter/) - Zed text manipulation post. [zed.dev/blog/text-manipulation-kung-fu](https://zed.dev/blog/text-manipulation-kung-fu) ### 🔖 Zettel Candidates - **Hosts evaluate Zed’s readiness today.** The episode frames a readiness review. [YouTube](https://www.youtube.com/watch?v=bRK3PeVFfVE) - **Pain points from earlier builds are fixed.** Signals rapid product maturity. [YouTube](https://www.youtube.com/watch?v=bRK3PeVFfVE&t=332) - **UI quality and themes impress out-of-box.** Defaults reduce customization time. [YouTube](https://www.youtube.com/watch?v=bRK3PeVFfVE&t=398) - **Zed marketplace remains less rich than VS Code.** Expect tradeoffs on plugins. [YouTube](https://www.youtube.com/watch?v=bRK3PeVFfVE&t=706) - **Rust-based extensions raise entry barrier.** Fewer casual plugin authors. [YouTube](https://www.youtube.com/watch?v=bRK3PeVFfVE&t=853) - **Git UI lands solid staging and diffs.** Core workflow meets needs. [YouTube](https://www.youtube.com/watch?v=bRK3PeVFfVE&t=1074) - **Problems panel improves triage clarity.** Quicker lint and type fixes. [YouTube](https://www.youtube.com/watch?v=bRK3PeVFfVE&t=1379) - **Language servers show status and controls.** Operational awareness matters. [YouTube](https://www.youtube.com/watch?v=bRK3PeVFfVE&t=1979) - **Split-and-move pane improves multitasking.** Side-by-side editing increases flow. [YouTube](https://www.youtube.com/watch?v=bRK3PeVFfVE&t=2338) - **AI works with Copilot or Zed models.** Avoids single-vendor lock-in. [YouTube](https://www.youtube.com/watch?v=bRK3PeVFfVE&t=2399) ## 🗣️ Paraphrase - The speakers review Zed’s features, speed, and UX polish. They compare it to VS Code and Cursor. - They highlight Git UI, problems panel, collaboration, AI, and pane management. They note a smaller plugin market. ## 📰 Newsletter - Trying new editors again? Zed feels fast and clean. - The Git UI, problems view, and focus mode shine. - AI plugs into Copilot or Zed’s provider without drama. - Tradeoff: fewer extensions than VS Code today. - Links: [Zed](https://zed.dev) • [Episode](https://www.youtube.com/watch?v=bRK3PeVFfVE) • [Tree-sitter](https://tree-sitter.github.io/tree-sitter/). ## ✅ Action Items #### DevRel - Publish a Zed onboarding guide for WordPress devs. Measure adoption and PR velocity. - Record a live demo: Git UI, problems panel, and LSP restarts. Track time saved. - Create snippets and tasks for WP projects in Zed. Ship examples. - Run a survey on editor usage across contributors. Share anonymized results. #### OSPO - Define an editor evaluation rubric: performance, LSP, AI, extensibility. - Assess license and telemetry for Zed and Copilot. Document risks and mitigations. - Pilot Zed within a team. Compare build times and defect rates. - Add guidance for MCP servers and AI provider choices. #### Community - Host a pairing session using Zed collaboration. Capture failure modes. - Build a “problems triage” checklist for themes and plugins. - Curate Zed tasks for npm, pnpm, and composer workflows. - Publish a cheat sheet for keyboard-first navigation in Zed. #### WordPress - Core: profile contributor workflows in Zed. Share bottlenecks. - Documentation: add LSP setup pages for PHP, JS, and CSS. - Accessibility: check exported patterns from editors meet WCAG. - Meta: evaluate Zed for .org tooling contributions. - Training: produce short modules on Git UI and diffs in Zed. - Plugins: template a “Zed-ready” repo with tasks and scripts. #### The WPOCC - Fund a microsprint on “editor ergonomics for contributors.” - Offer a fellowship to document editor setups for maintainers. - Publish budget and outcomes for tool trials. Ensure transparency. ### FAIR - Specify provider neutrality for AI in editors. Require local fallbacks. - Define provenance rules for AI edits and commits. - Ship operator agreements for telemetry and data retention. ## 🧪 Hypotheses - Zed reduces context-switch time versus VS Code in common tasks. - Zed’s problems panel speeds lint and type fixes by 20%+. - Split-and-move pane improves multi-file throughput in reviews. - Provider-agnostic AI reduces setup friction for new contributors. ### 📊 Methodology - Run crossover trials for 20 contributors over two weeks. - Log task times: staging, diffs, lint fixes, and LSP restarts. - Capture subjective UX via SUS and NASA-TLX surveys. - Analyze differences with paired t-tests and effect sizes. ### ❓ Questions - How stable is Zed across very large monorepos? - Does Zed’s marketplace pace hinder niche workflows? - How does collaboration handle privacy and compliance? - Are AI edits traceable for audits and rollbacks? ### 🔮 Future Research - Benchmark Zed on low-spec machines used by volunteers. - Compare AI completion quality across providers in Zed. - Evaluate PHP tooling parity for WordPress core work. ### 💡 Implications - Faster triage can raise contributor throughput and retention. - Clear AI options reduce vendor risk for organizations. - Consistent LSP control helps new contributors succeed. ### 🧠 Learning Styles Assessment - Reading level estimate: Flesch-Kincaid Grade ~9–10. #### 👀 Visual learners - Present: UI walkthroughs and panels. - Improve: side-by-side diffs and flow diagrams. #### 🔊 Aural learners - Present: narrated discussion. - Improve: 3-minute audio recap with tips. #### 🗣️ Verbal learners - Present: plain explanations of features. - Improve: glossary of Zed terms and keys. #### 🧩 Kinesthetic learners - Present: hands-on steps for Git and LSP. - Improve: short labs and checklists. #### 🧠 Logical learners - Present: structured comparisons to VS Code. - Improve: decision trees for provider choice. #### 🧑‍🤝‍🧑 Social learners - Present: collaboration feature overview. - Improve: cohort pairing guides and norms. #### 🧘‍♀️ Solitary learners - Present: focus mode and shortcuts. - Improve: self-paced exercises and quizzes. #### 🌿 Naturalistic learners - Present: none noted. - Improve: energy and performance metrics. ### 📊 Accessibility Assessment #### Screen reader semantics - Present: depends on web output, not editor UI. - Improve: ensure headings and labels in WP projects. #### Keyboard navigation - Present: keyboard-first workflows highlighted. - Improve: publish default keymaps and alternatives. #### Contrast and readability - Present: themes vary; defaults look strong. - Improve: recommend accessible themes and font settings. #### Text resizing and reflow - Present: UI and editor font controls exist. - Improve: document zoom and reflow behaviors. #### Media and captions - Present: YouTube provides captions. - Improve: publish full transcript alongside summaries. #### Forms and interactions - Present: N/A for editor internals. - Improve: in-repo issue templates aid accessibility checks. #### Standards reference - Map docs and outputs to WCAG 2.2 AA criteria. ### 🌍 DEIB Assessment #### Cultural breadth - Present: general dev audience. - Improve: include non-English resources and locales. #### Inclusive language - Present: casual and friendly tone. - Improve: add plain-language summaries for beginners. #### Neurodiversity support - Present: focus mode and keyboard-driven UX. - Improve: predictable structures and consistent keymaps. #### Representation - Present: hosts’ perspectives. - Improve: invite diverse contributors for tool reviews. #### Psychological safety - Present: respectful discussion. - Improve: publish contribution norms for pairing sessions. ### ✅ Logical Validity #### Strong reasoning - **[H6] Git UI now meets needs.** Evidence: concrete staging and diffs. Show tasks and timings. - **[H7] Problems panel helps triage.** Evidence: quicker navigation. Add measured fix times. - **[H12] AI supports multiple providers.** Evidence: Copilot and Zed options. Clarify setup paths. #### Fallacies - **Overgeneralization risk** at [H4]. Smaller marketplace may not block all workflows. Scope by use cases. - **Appeal to novelty** around speed claims. Provide benchmarks and tasks, not vibes. #### Tone of voice - Conversational, practical, lightly humorous throughout. Examples feel concrete. ### 🛡️ DARVO Analysis - Deny: none observed. - Attack: none observed. - Reverse victim/offender: none observed. - The segment remains evaluative and constructive. **Tag Coverage —** #articleseed: 4 • #xref: 3 • #share: 2 • #bmf: 0 • #addendum: 1 ## 🎯 Conclusion - Zed appears production ready for many workflows. - Expect speed, clean UI, and solid Git and problems features. - Plan for fewer extensions and some AI setup steps. - Next: run a team pilot and measure concrete outcomes. ## 🧱 Refactor Appendix (append after 🎯 Conclusion) ### 📚 Literature Split Pad - Purpose: Stage Konik CEE units that become per-source Literature notes. - Split level: **H3**. - Include verbatim quotes under 25 words and a [view highlight] link. ### [H1] 5–10-word present-tense claim > [!quote] [Zed is Ready For Primetime](https://www.youtube.com/watch?v=bRK3PeVFfVE) by an unnamed author via [[YouTube]]. Published [MISSING]. Accessed . > “Today we’re going to be talking about zed.” Two lines: scope and intended coverage. [view highlight](https://www.youtube.com/watch?v=bRK3PeVFfVE&t=87) #xref #articleseed ID:rw_[MISSING] ### [H2] 5–10-word present-tense claim > [!quote] [Zed is Ready For Primetime](https://www.youtube.com/watch?v=bRK3PeVFfVE) > “The UI looks awesome out of the box.” Two lines: defaults reduce customization time. [view highlight](https://www.youtube.com/watch?v=bRK3PeVFfVE&t=398) #xref ID:rw_[MISSING] --- ### 🔖 Atomic Split Pad (Zettel Candidates) - Purpose: Promote reusable claims into Atomic notes. - Split level: **H4**. - Each item: one idea, present tense, specific, testable. #### [Z1] Zed defaults reduce setup time - Applies to new installs and trials. - Evidence: out-of-box theme comments. - Links: [[Editor-UX]] [[Onboarding]] #### [Z2] Problems panel accelerates lint fixes - Applies to JS/TS and CSS warnings. - Evidence: targeted navigation in panel. - Links: [[DX-Metrics]] [[Linting]] #### [Z3] Split-and-move pane boosts throughput - Applies to reviews and multi-file edits. - Evidence: one-command side-by-side. - Links: [[Code-Review]] [[Flow-State]] #### [Z4] Marketplace maturity limits niche workflows - Applies to extension-heavy teams. - Evidence: smaller catalog. - Links: [[Ecosystem-Risk]] [[Workarounds]] #### [Z5] AI provider choice reduces lock-in - Applies to regulated environments. - Evidence: Copilot and Zed options. - Links: [[AI-Governance]] [[Vendor-Risk]] --- ### ✏️ Fleeting Queue (Extract by Selection) - Purpose: Capture quick actions or sparks for Fleeting notes. - Extraction: **Select one line** → “Refactor: Extract selection to new note (content only).” - Keep each line short and self-contained. - [F1] Record Zed Git UI demo — context/17:54 https://www.youtube.com/watch?v=bRK3PeVFfVE #fleeting #inbox - [F2] Draft Zed keymap for WordPress — context/30:13 https://www.youtube.com/watch?v=bRK3PeVFfVE #fleeting #inbox - [F3] Write AI setup doc for Copilot — context/39:59 https://www.youtube.com/watch?v=bRK3PeVFfVE #fleeting #inbox --- <!-- deep-read:sections end --> ## 📺 Video ![](https://www.youtube.com/watch?v=bRK3PeVFfVE) --- # 📄 Full Transcript *Auto-generated from YouTube captions · timestamps roughly every 30 seconds · [watch on YouTube](https://www.youtube.com/watch?v=bRK3PeVFfVE)* **[00:00]** Before we get started, two things. Meetup and spooky story submission. We need you for both. October 27, we are going to be doing a meetup in San Francisco at Bear Bottle Beer Garden in Salesforce Park. We're in town for GitHub Universe. You don't have to actually be going to GitHub Universe to go to this. It's open to anybody. We're going to have a bunch of drinks, a bunch of swag. Really good time. So, if you're anywhere in the California area or somewhere in California or anywhere you want to fly down, come on out. October **[00:31]** 27th, it's going to be a hoot. Go to syntax.fm/meup and you can grab a ticket. They are free, but you do have to reserve one because space is limited. Second, Halloween's coming up. We need your spooky stories. This is an episode we do every single year where we read off the most terrifying spooky stories about web development in general. So, have you taken down prod by accident? Have you published something that you shouldn't have? Have you let an SSL certificate expire? Have you dropped a database by **[01:02]** accident? Deleted all the records. We want to hear your most stick your head in the ground stories for Halloween. These are always awful to hear, but you learn a lot. So, please go to syntax.fm/spooky and submit your story. We keep absolutely everything anonymous, so tell us your worst. [Music] Welcome to syntax. Today we're going to be talking about zed. Zed is the new hot **[01:34]** editor that's built in Rust. It is not a fork of VS Code and it is fantastic. So, we're going to be talking all about why you should pay attention to zed in this episode. My name is Scott Tinsky. a developer from Denver. With me as always is Wes Boss. What's up, Wes? >> Hey, excited to talk about Zed. I've been like dipping into it every I don't know four or five months just to kind of see where it's at. Beta testing some of the features, but I've never given it a full like a college try, you know? So, **[02:07]** I'm curious to see where we're at right now with zed. Also, I appreciate that they call it zed, which is what Canadians call the letter Z. >> Is that so? >> Yes, >> they do. >> We do. I don't say >> I don't. Zed Zed is actually, let's be real, zed is a dumb name for a letter. We should have called it Z. That sounds much cooler, but it's a good name for an editor. So, tell me about it. >> Yes. Oh, I'm actually going to push back. I think zed's a cooler word than Z. I'll be honest. >> All right. >> Sound off in the comments, folks. Z or zed, what do you think? All right. **[02:38]** Before we get going, though, also cool thing, Century. Century.io, the perfect place to solve your problems on the web. Man, let me tell you, I've been using so many of the Century tools lately in some of my developer flow. There's a really great tool they have called Spotlight, and there's a new Spotlight MCP where you are using essentially all of Century's tools locally, which is so great when you're working locally because you can get access to better debugging tools. It's capturing errors. It's it's doing all kinds of things and **[03:08]** you're not having to necessarily rely on really deciphering uh some awful error that's in your console that you have no idea. And with their MCP server from your AI code, you can actually talk to Spotlight directly and see if it can help you get some answers on this stuff. Cuz oftentimes, Wes, we think that the hardest part of our our job is fixing the bug. But I was thinking about this a lot. The hardest part is not fixing the bug. It's finding the bug. Fixing the bug is the easy part. So once you find **[03:40]** it, you can fix it once you know what's going on. Once you Yeah, >> it's true. Like debugging sucks cuz you are trying to figure out what went wrong. You know, often the the code mistake is is not huge. It's actually trying to piece it all together and and get all the clues together. >> It's solving a mystery where you were essentially the killer yourself and now you have amnesia. So now you're you know >> why did I do this to myself? >> Why? Yes. Why? Cool. So let's get into it. Zed. Zed is a you know I say new **[04:12]** because it's it's new relatively. Um but I I've had Zed installed on my computer for a while now. And um I pop open Zed every now and then. The very first time I started working with Zed was pre plugins and extensions. And so it was like here's this barebones new editor and the main thing about it is that it's fast. And then I uh once extensions and plugins came out for it, I was really quick to write a syntax theme. I was **[04:44]** actually one of the very first extensions uh was the syntax theme on Zed. So I've been a longtime observer of Zed, checking it out. And more recently, I kind of put the snooze button on Zed for a while. there was a number of uh key features that I use every single day that I just found myself missing and unable to get past and I am happy to say that most of those things have now been added along with a tremendous amount of other things inside of Zed. So, we're **[05:15]** going to be talking in this episode a lot about why you should care, what does Zed offer, what is novel about it, and like what are some little neat things about Zed? Basically, what's the deal with Zed? Is it ready for prime time? Spoiler, yes, it's ready for prime time. It's sick. It's great. Cool. So, that said, what led me to start picking up Zed again? Big one. There is a bug in the latest Mac OS uh involving Electron where Electron was using some private **[05:45]** API on Mac OS leading to just a massive memory leak on any Electron app that you were using. >> Yeah. So whether that was Cursor or VS Code or any of the VS Code uh forks or anything like that, man, my system, which shouldn't be grinding to a halt, was just dying. It was, man, the fans were running all the time on this M1 and it was just crazy. So that led me to saying, you know, like maybe it's time to give Z another try and maybe I can get past some of my annoyances. And then **[06:17]** when I popped it open, imagine my surprise when all of my annoyances had been totally fixed. And not only that, there's so much more. So, let's talk about it. I have for video users, I will have the UI open um so you could just see this in action, but like audio listeners, you're not going to be missing anything other than what it looks like. And let me tell you, the number one thing I like about Zed, besides the fact that it runs really well, performant, doesn't eat up a lot of memory or anything like that, the number one thing I like is that the UI **[06:49]** looks awesome out of the box. If you're working with a an a UI based text editor, the UI looks fantastic out of the box. The themes look great. I mean, obviously, there's there's a host of themes if you don't want um the ones that come installed on here. Like I I've been installing what is this? Luxe light. I like this theme a lot for a light theme. Picture me using a >> Yeah. What the heck, Scott? Why you switch changing editors and using a light theme here? What happened, **[07:19]** >> bro? Uh I started working in my car a lot during light time when it was like I'm taking the kid. My daughter has two hours of dance. Now I'm working out of my car. So what am I going to do? of the you know it's like the working on a light mode in the middle of the day is actually really really nice but I can't go full white I have to do like a >> sepia tone one yeah I had to go like solarized kind of style so yeah I know >> okay I believe you owe me an apology **[07:50]** light mode is awesome I actually don't use light mode in any of my editors or like whatever but I do use light mode in a lot of my like apps like notion light mode all day. >> Yeah. Yeah. You know, I all it took for me was like finding the right light mode and then once I did it was like >> uh Oh, this is great. It's Noctis, by the way. Noctis is the package. And there's a ton of Noctis light and dark ones, but I use the Noctis Light Lux is **[08:20]** the one I like the most because this feels kind of nice. This is lilac one's pretty uh pretty dope, too. It's kind of like purpley. Yeah, >> it is a nice looking editor, though. And I think that's really important cuz like I spent all this time trying to tweak my VS Code and I'm still not totally happy with it. And I I find the same thing with my my warp editor as well. I'm just not happy with how it looks at all and there's no control. But like out of the box, this thing looks fantastic. I don't know if it's that it's different, but it's like the right density of **[08:50]** information for me to be happy. >> The one thing that VS Code has never had, it's never looked good. And I and I don't say that to be mean to anybody, but like even when Atom came out, there was Atom was the, you know, text editor and even Sublime Text looked better. When VS Code came out, I was so reluctant to use it at first back in like what, like 2015 or whatever. I was so reluctant to use it cuz it looked so much worse than what I was using. And they never really got a handle on how it **[09:21]** looks. And for some reason, whether it's the icons or the spacing, the text, whatever, this thing looks great out of the box. So, uh, shout out to the Zed team for having good design chops. One thing that you'll you'll notice about Zed is that it's not just kind of the general editor experience that looks nice. It's like all of the different panes and windows. Uh, I'll talk about a lot of these things as we go, like the Git UI and um, you know, the the diff modes and stuff like that. Every single window in this thing looks really nice **[09:52]** and doesn't feel like it was just kind of slap dash put together. It feels like it was all made for this. Video users will see that there is some like white text on a yellow background. That is a problem with my theme specifically. So if you see that, that is uh that's egg on my face, not the Z team's face. So uh really what it is is that I built this theme before that feature existed. So I need to update my theme. Cool. So, let's talk about uh besides just general editor experience. It should feel very at home. A lot of the shortcuts are the **[10:24]** same as VS Code, so you you'll really feel like getting back into this thing. Should feel pretty normal to you. Uh there is an extensions marketplace which uh came about a little while ago. A shift command X does in fact open that the same way it does on VS Code. extensions run from anything from language servers to themes to icon themes, uh, grammarss, MCP servers, snippets. So, there's a lot of like nice things in here. What's interesting about this is that they do nice job of the **[10:55]** filtering and extensions UI. Um, like in VS Code, it's that little sidebar and you're kind of like always struggling to see. You click on it, opens up where here, it's like it's the kind of the star of the show. They have a nice little uh UI for installing extensions which I I just find to be a nice UI. There is one complaint about this UI is that you cannot get to the readme of any of these things uh without clicking on the GitHub logo. You click on the GitHub logo, it pops you open in another **[11:26]** window. So, you can't just get to that that I mean that's not that's a huge annoyance. You always have a browser open, but it would be nice to click on this and have it expand or open up to be able to see the UI for what these things are cuz sometimes the the plugins they they're not exactly explicit as to what they're doing. So that that's a bummer. Uh and the extension marketplace, I will say, is not as rich as VS Code. So that's another slam on on Zed. There are just like there's a handful of **[11:56]** extensions that I would like to see in here that like I was trying to think about like what extensions am I really missing? And one of the big ones for me would be like being able to npm install something. So like if if I wanted to command p npm install, you know, that that doesn't exist in here out of the gate as a command and there's no extension for it. Same with like PNPM, which is something I actually did kind of a lot. I don't know. Do you do that, Wes? No, but I I don't love my workflow **[12:30]** for for npm installing something because like to me that's that's probably something that should be done in the terminal, but then I find myself having to open up a second tab to mpm install something because I'm running a process in that or you like you send it to the background whatever like you FG I'm not a for no you send it to the background and then it like pauses that and then you npm sol. So maybe the editor is the spot. >> Yeah. You know, the one extension I've been using in VS Code uses ni, which is **[13:02]** the one that detects if you're using PNPM, yarn, or npm for that project and runs the appropriate thing. >> So like I've just been doing like ninstall whatever directly from the command prompt within VS Code. And that to me has been like a really nice workflow cuz again, what else am I going to do? I'm going to make a a duplicate tab of the the terminal window. then I'm going to install it, then I'm going to close that duplicate tab and then do it again next time or I forgot to install something, right? So, I've been doing all my installs directly from there. It **[13:33]** would be nice to have that in here. Uh probably feels like a fairly trivial extension to add. Uh so, who knows, maybe I'll even not >> I'm just looking at the type of extension, right? They have themes and icons. There's there's languages and grammarss for highlighting. There's language servers which like you talk back and forth to like a TypeScript server, MCP server, snippets, and debug adapters. I don't know that any of these like these all seem config based. I I don't see anything that would have like **[14:03]** custom logic in it. So like do they have the ability to do that? you know, like maybe they don't have the the UI stuff in place yet so that people who want to make like a some sort of custom v extension >> to do. Let's see. Let's let's look it up. Zed extension authoring. >> Looks like the debugger extensions can be written in Rust. And that's the the benefit and the downside to a lot of this stuff is that if the extensions **[14:34]** must be written in Rust, they're probably going to be faster and great. But like not every idiot like me can just go ahead and whip up an extension really quickly like like like JavaScript, right? That's the the huge benefit to the VS Code ecosystem. But the I think there's also some some benefit as well of just like leaving a lot of that stuff behind, you know, like at a certain point you have to just like you see it with like ESLint as well. You know, people are just going to move to to biome and be like, you know what? >> Yeah, >> I'm not going to try to fuss with this **[15:05]** anymore. I'm just going to switch to something entirely different >> or similar. I guess >> it does seem like extensions can define tasks. And tasks are a thing within zed that are repeatable kind of actions. >> So I'm not that verifying that uh you can in fact do this but >> I you know it seems like a program with arguments a shell with arguments could be **[15:35]** >> done as a task. So >> yeah and you I guess you use JavaScript in in that point. That's probably a little different if you want to interact with the Z UI, but yeah, tasks you can as long as you can run a command, right? You can you can run whatever you want. Yeah. Yeah. So, we'll see about that. But yeah, so I I found that to be to be pretty interesting. But again, the extensions, as you can see, the fact that you can like, let's see, go to any of the extensions page and you can actually scroll to the bottom of it should give you an indication that like the extension market isn't as rich, but **[16:07]** there's also probably not as much junk. Another thing I found to be commonly true with this editor is that a lot of the things that you would have turned to historically an extension for in VS Code, they do just kind of exist out of the box. like CSS, you know, the colors in VS Code, the color highlighting just is here out of the box. So, it shows you the color. So, like stuff like that that you may have installed an extension for just kind of exists inside of here. And that's nice. >> My theme, so I I I made Cobalt 2 for **[16:39]** zed. Actually, somebody started it and then I tweaked it >> and they they passed it over to me. 20,000 installs already. So, that's that's not nothing. That's that's significant amount of people like going out and looking for my theme on Zet, you know, like it's not like it's HTML or or ESLin or something popular that everybody wants. It's people that explicitly want that theme. 0.0.1 version of the syntax theme also has 20,000 downloads. So, uh, I got to update this just a little bit to make **[17:10]** sure that yellow on white text thing doesn't happen. >> Yeah, you're right. >> 20,000. Not bad. It's a good-look theme. I will uh toot my own horn there. It's a good-looking theme, folks. Thanks for no selling me on that, Wes. You just complete silence. I say my theme is good-looking. It's a syntax theme, and you just have complete silence. >> You know what I was doing? I was installing it. Let's Here we go. And I'm I'm going to turn it on in my own theme. Syntax looks nice. Okay. Okay. I like it. I kind of want to go every now and then. I think my Cobalt theme is a **[17:42]** little light on the light side for for me. I kind of want to go a little darker. And I turn this on, I see pure black. I like that. >> It's black, baby. >> Yeah. >> Yes, that's for sure. Cool. All right, let's talk about the Git UI. Um, this is one thing that held me back from using zed in the past, which seems silly because it's it's like I can use git in the command line, you know, but in the same regard, like I got really used to coming into VS Code and uh let me see, I **[18:14]** can't really bump up the interface that much. I got really used to VS Code and the git UI in VS Code where you type in your commit message, you you sync and and do all that stuff directly from VS Code. Again, specifically for the reasons that I I mentioned about the terminal thing. I just got so used to doing it without having to pop open another term window, especially because I don't like using the ineditor terminal anyways. So, I had like ghosty over here and I don't want to have to pop open a new term. So I I can just do it directly **[18:44]** from here. And I was really pleasantly surprised with the Git UI, especially since they didn't have it before. And that's something I think rings true for most of uh this app is that when they do something, they do it well. So the Git UI is really nice. The diff editor looks nice. Um you can come and stage or restore. Stage or restore. Um, nice language on everything, not just kind of like I mean there are icons throughout this, but the icons are fairly explicit. **[19:15]** Um, oh, you can go to next hunk. So, we can we can browse hunks in Zed. >> My nickname in high school. >> Yeah, go to next hunk. Uh, she sees Wes. Okay, go to next hunk. >> Oh, brutal. By the way, you can update the font size of the sidebar. Just go to your settings and change UI font size to something a bit larger. >> UI font size. >> Okay. And that's not the editor font **[19:46]** size. Okay. That's the buffer font size, >> which I love that because often I want to crank up one of the two. And you can do that in VS Code, but it's kind of tricky where you have to make one. You have to zoom in and then make something a bit smaller. I like this a lot better. So, folks who are now seeing on video, uh, the UI definitely looks uglier that I bumped up the font size, but you'll now at least be able to read things or see things a little bit better here. Um, so hey, the get UI on this thing I think rips. And I'm happy it's here because again, this is something that I really really wanted in this. I just got so **[20:18]** used to it in VS Code that like not having it actually became a bummer. It's not like I can't use git on the command line, but again, it's just an annoyance, right? So, you say you you've like moved like almost all of your your git interactions into into the editor. >> Hell yeah. >> All right, man. I I've slowly been moving it over and the one thing that has has got me is the AI commit description. Love that. You know, can't think of what I did. I don't even know what I did, but the AI does. **[20:49]** >> Yeah. >> You know what? I've I've been using instead of like, so I' I've been using change sets a Have you been using change sets ever? >> I maybe what what's a change set? >> Change set you're kind of like it is kind of like a commit in a way but you are creating a file that defines like a description of like what was changed and then it can apply version updates and write a change log for you. So I've become the kind of opposite of that where I'm becoming like more intentional with releases and change sets and like **[21:22]** really writing things out. I don't know why, but I like it. >> I especially like when projects use that because then you can just go into the change set and see what has changed. Or if you're in a branch that's not yet released, you can take a look at the change set and see what has has been done in this branch. >> I've been working on a handful of like open source projects that I just like it becomes very nice when you're changing versions via CI for that kind of stuff. like uh zero spelt. I I got into change sets just because I was like, you know what, I'm sick and tired of manually **[21:53]** updating the versions and doing all this stuff. Let me get deep into GitHub actions. I added change sets. I added all that kind of versioning, automatic versioning and publishing via GitHub actions. >> Beautiful. Yeah, so smooth. >> Back to zed. The problems UI is really nice. And let me bump that open over here. So when you have problems in your code again whether that is from your prettier your llinter any of that stuff VS Code man it just like it's either like the inline problems view is like **[22:23]** the only way to look at that in my mind cuz when you pop open any of those problems panels in VS Code man that is like often very painful for me. I don't know how you feel about that. >> Yeah it's not a great UI. I I I'll give you that as well. like I don't often when I need to go into it like if you want to see what's wrong with a file you want to go through it I I don't love it you know it's just it's not a great UI it's not and so in zed when you pop open you'll see when you see little problems **[22:54]** problem diagnostics in your in your bottom toolbar um you can open them with shift commandm it pops it open and then it kind of gives you a file by file now again I have this yellow unknown property warning that as again it's problem with my theme here. Um, but like here's this one. Box shadow is already defined here. So I have a duplicate definition for this box shadow for some reason. Probably because I was tweaking the style at some point. And then you have like a a TypeScript error here. Locals has implicitly any type. Okay. So **[23:24]** uh so you could come in and fix it directly from here or you could then do op uh it says option enter. >> That's cool. But is it option enter or is it >> that's alt alt enter because you have the alternative option of taking the stairs. It's a little man on a escalator. >> That's how I remember. >> I love that. >> Yes. >> It's like why? Yeah. I'd never heard that. So you do alt or option on the Mac key enter and it jumps you right to that file and then you can fix it from here if you want to do it outside of this **[23:55]** interface. But man, this is this is a great little let's knock out all my problems. Let's take them out. uh you could see you got to be able to do that cuz VS Code has >> all of those things, you know, like in if you're looking at a git diff and you want to just see what has changed, you got to be able to do that cuz that is a really nice UI, you know, show me the code. I can edit it right there, but show me all of them and you can you can fold them. That's that's great. I like that a lot. >> Yeah. I think my problem with it in VS **[24:27]** Code is that it's part of this bottom panel. like yeah they are kind of listed out here I don't like >> right and and like the big problem with this to me is that like this panel is probably the single like my least favorite part of VS Code and it's the one reason why I don't use the terminal cuz I just don't like it. it's always popping up in the way and then you there's just like a lot of stuff in here like >> it it's something to be said for for like the UX of it because of of course you can make it work how you want but **[24:59]** >> like I don't I don't know how to make it work better you know just show me like like Zed you know the default experience is really good and like VS Code is so many users that like if they were to change the default experience on that they they have changed the default experience on several things and what they do is they roll it out for a certain number of people initially and and see if what the feedback is. But like >> man, there's so many people. It's so nice that Zed can just like kind of do this from the get- go. And and that's **[25:30]** the same for a lot of stuff with this Zed is they can choose what all of the stuff will be like instead of having to tack it on after the fact cuz they're they're still building it. And it shows I think it really shows in the care that is expressed throughout this app. Uh which I really love. Like every single little menu on it looks nice. Every UI looks nice. Find and replace looks nice. All the stuff. So we got get UI. That's a big one for me. The problems UI really **[26:00]** nice. Uh they also have a real time collaboration feature which isn't something that like I personally have been dying for. It's not a feature that I would use extensively, but I think it's really neat. So, the collaboration tools is that like you can essentially uh invite someone to your uh project. If somebody has a Z account and they're in your contacts, you can add them and invite them to a call and then they can **[26:32]** get voice chat along with that. So, it's pretty neat that you can collaborate in a codebase running on one person's computer and actually even get chat through this. Again, it's this is not a feature that I've been dying to use. So, my experience in this is non-existent. I'll tell you that. I've read the docs. I've checked it out. But for those of you who do like uh remote paired programming and that kind of thing, I think this could be a really interesting feature. Burke Holland from VS Code was **[27:02]** tweeting the other day how I think he was how like live share is the VS Code version of that. >> Yes. >> In fact, they deprecated the voice thing and I don't think a lot of people use it. >> It's there and and not a lot of people >> I don't I don't think a lot of people pair program and if you are pair programming maybe you're probably using something else. Yeah, if I recall correctly, um during my live chat with him, he said it was like the one feature that was like really requested and then never used. Like people would say they want it and **[27:34]** then nobody was actually interested in using it. But it looks neat. I will say that. Some other little neat things about this app is that there's a lot of nice little stuff baked in to the uh command prompt. Um so if I like select a variable, I can convert to title case. And like this is stuff that you can do in VS Code obviously, but it's an extension on VS Code. Convert to uppercase, upper lower camel case is uppercase. Okay, they call Yeah, I would **[28:07]** have called the screaming snake case, but it's just uppercase. So >> Oh, did it did it just did you just do that on the the import and it it swapped it? >> Did it actually swap it in the import? because I'm wondering if that's using the the VS Code language server like it it communicates with the language server to do a smart replace. Do it again. >> So, no, it just swapped what was underneath my cursor. So, this one is now >> Okay. >> Yeah, in VS Code there's like usually like a rename symbol and that exists here too just with F2 rename symbol. Um, **[28:38]** so that certainly exists. Code actions is the same. So, command period does code actions as well. So like you can fix with AI assistance, suppress, lint, all those typical type of code actions you might expect. And that's the one thing I think kills is that like so many of your cheese has not been moved, right? Like your your stuff's there. Uh so I I tend to like that quite a bit. >> Yeah. You got to you got to be able to move over and feel comfortable relatively quickly with these new tools. **[29:09]** Otherwise, it's just frustrating all the way down. >> Totally. Yeah. especially uh you know thing I really like too is that on any given file if you do controlloption L or just click on this little icon it shows you every single one of the language servers that is currently running and this changes based on which file you're in. So uh the package version server is not running and the JSON language server is not running because this is a spelt file but I do have biome I have live **[29:39]** server I have uh markdown oxide I have all of these things that are currently running and you can again restart all language servers or stop them all from here. So that's a nice little UI. You know how many times you're like restart Typescript language server or any of that stuff? um just to be able to have confirmation that things are running and actually like up with a little status light if you wanted. It's there. I just I like that. Um another cool thing is there's a zoom in which is just um shift escape. A shift escape just kind of pops **[30:11]** open whatever file you're currently active and makes it full screen. And a shift escape will make you back to your editor. So that's just like uh if you want to get rid of the distraction instead of hiding your chat windows and all your other stuff. Let's say you got a whole bunch of stuff open. Um your AI chat, any of that stuff, you can at any point just have it go full screen instead of closing all the other stuff. So that's a nice little uh UI. >> Does it does it pop over everything? >> Yes. Pops over everything. Yes. >> Oh, that's really nice. I like that a **[30:43]** lot. I never thought to do that because like I have like three or four little shortcuts that I use to close everything or you can just flip into like zen mode. But that's kind of nice, you know, >> and it's an easy it's an easy shortcut, too, you know, so it's not one you're going to be like reaching for or like scrambling to hit. >> I'm going to be implementing that. That's great. >> Yeah, brother. And uh let's talk about AI stuff cuz you know, we just had a monster video on the channel talking about uh how much AI >> crashing out over AI. **[31:14]** >> Yes, TJ absolutely going nuts over AI. Uh, yeah. You know what's cool is that the AI stuff you're probably used to is in here, too. So, there is hints if you want inline hints inside of your editor. LM provider is not configured. Okay. So, I I'm sorry. I'm using Copilot, so my uh things are a little bit different here. Either way, there are inline hints, which are nice. I don't feel like it's cursor good, but it's it's there. the chat panel can use cla code with their **[31:46]** not even like cla code's UI. So if I pop this open, it just inherently uses cloud code and it uses your given cloud code setup. It's not some like weird sandboxed version of it. So I asked it the MCP servers and it listed all of my global MCP servers. So it required no configuration. And since I am already using and paying for cloud code and I already have it all set up, I don't want to have to set that up again inside of the editor. I've been using this instead of my ghosty terminal uh for cloud code, **[32:18]** which has been nice because it gives you >> like a approval UI too. So like I can reference files the same way you would in like copilot. Say make this I don't even know what to say. I don't even know what to tell AI these days. I don't know what to say. Make this purple. >> Yeah, do it. >> Make page purple. Okay. Um, this is a spelt page, so it's probably going to try to add some styles here. Whatever, it's going to do it. It's going to uh give you that **[32:49]** approval, right? Always allow. Okay, I'm going to click allow cuz always allow is kind of whatever. But if you allow it to edit the file, does give you the keep or reject. And it is a nice little command Y or command N for yes or no. So if I wanted to accept this or or not. And there it's gone. Right. Uh so the the AI chat interface is great. You don't have to use cloud code. There's even a zed specific AI like their own which I have not used. >> Like if you if you're paying for cloud **[33:19]** code or co-pilot or whatever, you can bring your bring it along. You don't have to pay another fee for this. >> Yeah. Or you can pay them to use theirs. You can install MCP via their extensions if you want or you can use the cloud code ex or yeah any of that stuff. And the C-pilot stuff was easy. I just clicked whatever I installed via GitHub and next thing you know I can use any of the co-pilot uh models if I want to throughout this or I can use cloud code throughout this. So AI features they feel very comparable. They feel very **[33:50]** nice in here. They're not giving me, as far as I know, an AI commit message, but hey, can't win them all right now, right? >> What about like um something that I'll do is if you have either you have an error or you want to like like copy some code and add to chat? Does that exist? >> So, command. So, you uh Oh, that's interesting. So, let's see. Let's see if I I probably just don't know the um open in terminal copy reveal and finder show **[34:21]** code actions for yeah I don't see an add to chat here. What was interesting is that there was a fix with assistant when there was a problem but when I would just highlight something normally and do a code action on it. If I do fix with assistant there is a an inline chat AI chat directly in here. But I don't see an ad to chat the same way you do in VS Code. >> That's something I need a lot of either adding a slice of code or like **[34:51]** referencing other Yeah, you can reference other files in it just with the the amperand. That's good cuz I'm trying to think like like what are the ways that I use AI in the editor, right? There's obviously the tab completion is is probably my favorite meaning that like I can't live without that and that's one of the things that stops me when I go back to VS Code. I try it every now and then and the tab completions on cursor are just so good. Then there's the AI commit message. I can live without that. There's the agents. Um seems like that's pretty good **[35:23]** as well. And then there's also the like fix this error um where you have like a squiggly in it and you can I use that quite a bit as well. So, it seems like they have most of those except the tab completions. They have them, but they're not as good. Is that what you said? >> Uh, you know what? It could be a user error at this point. And what's weird is that I have them working. And now if I click, it says LLM provider is not configured or does not support the configured model, which honestly uh I've been tweaking this stuff. I don't know which LLM provider it's even trying to **[35:54]** use for that. So, >> I got to figure out that part of it. But when I was I was I was having issues but I was also having issues with VS codes at the same time. So for me I was like is this just something that is wrong with my current setup? I I I wouldn't say I have evaluated it to a professional degree to to give you an answer if it's good or bad. >> All right. Because I'm pretty sure they had that at one point. I remember DMing with several of um the people that **[36:24]** worked there and trying it out. They gave me some key where I got like a a message, but there's not something. Yeah, I can't get it to to show up either. That's another frustrating thing about these things is when somebody hasn't touched the product in 6 months and they go back to it to to try it out, how do you let them know about all the new features or how do you >> Yeah. >> migrate them from where they were into the new one without making it too obnoxious as well. >> Totally. I actually ended up having to go through my settings file and manually **[36:56]** delete things from my settings file that existed from prior versions. It was like your settings file is super invalid cuz last time you opened this it was a completely different app. >> Oh, so the reasons why I avoided using uh Zed again was there was no plugins which are solved. Uh there was no git UI which is solved. Uh, there was no split and move pain, which I feel like I'm the only person in the world that uses this feature, but I do and I I'm like upset **[37:27]** about when it wasn't here. And then there was no AI chatter completions, which there now is people who don't know the this split and move pane. I have it locked to Hyper S. Nobody understands why I need this, but sometimes you're working in this file and I would like to have this file and another one open at the same time. And typically what a lot of people do is they split and then close the one window. Uh VS Code had that in one fell swoop where you could split a window and then move it instead of just splitting and having the same **[37:58]** file open twice. Now luckily inside of here inside of I think a keyboard open key map I don't even remember what the setting is. It is uh I think it's just like move to the left or something. Either way, I have it now and I do hyper s and look. Boom. Look at that people. How am I the only person who works like this where you have two files open, you want to have them split side by side, one command, now you have two different files open side by side instead of splitting it. **[38:28]** >> Yeah, I never understood the default of that being the same file. Like, who wants that? I guess the people who want that is like you have a really long file >> and you want to like scroll to the bottom while you keep the top open. But that's not nearly as common as I want to see two files at once. >> I want to got my my CSS or whatever over here. I want to have two components open. Whatever. Yeah. So thankfully this is here now. So the answer is is that it's uh workspace colon move item to **[39:00]** pane in direction and then you can give it the direction. Thank you Zed team. This is the one thing I really wanted. >> The tab completion actually is very good in Zed. I just got it working as well. It detects where you should jump to, which I really like. So, if you make an edit and it thinks that you want to put your cursor eight lines down to continue on, it will it'll tab that. It seems to know what I want with the little ghost text. So, yeah, big fan big fan of that. What configured provider did you use? I **[39:33]** think I'm using the man I've I've had this thing hooked up to my own LLM at one point like like my own key. I had the old Zed version. I had like a pro version. I think that I'm just on the right now just on the free zed LLM trial. >> Okay. >> Cuz I don't I don't see any other here. Agent defa Oh no, this is agent default model provider zed.dev. No, this is from this is from over a year ago. Last time I tried it, that was for the agent talking back and forth. **[40:05]** The actual tab completions are I think built into Zed. Uh you got >> it does say that you can use co-pilot to do. So at some point here, which is maybe when mine was working and now it's not. Uh some point I need to like change whatever the configured >> uh model is and change it to Copilot. Uh, Copilot's great because it gets you access to all of the models that Copilot has. So, GPT5, all that stuff directly in here. Before we get out of here, **[40:35]** things that it's missing. I think that it's missing some extensions still. I'd mentioned like really wanting some sort of like npm install extension. Not that I need it, but I I think I just like that workflow. I was trying to really think about it and I don't know too many other extensions that don't exist that I I want, but I'm sure I'm very positive there are some extensions read me in the editor. I I just want that. You don't always need it, but it's nice to be able to see what's going on, >> man. Like I I don't know if I could **[41:06]** write some some Rust to make this happen or not. Or like maybe they could make a compatibility layer with some of the VS Code APIs. That would probably be a big big project. But I would find it very hard to leave all of my comfy extensions. >> We found a Z comment here which is a uh looks like it's a better comments kind of alternative >> to do hack fix me. whatever. And it does highlighted colored comments. Looks like **[41:36]** the uh you can config, too. So, um that seems like a nice little uh >> here. Let's let's look at the code for this. Like, how hard is it to write this? What what's the link? Can you send me this? So, it's a SCM file. This looks like a like a syntax grammar file where it's >> Yeah. >> And then there is a Starcraft map file. This see it's 30 lines of this weird **[42:08]** code. What the heck is this? Oh, that's a tree sitter. Oh, tree sitter highlighting grammar written in Scheme. Oh, >> for the Z editor or any editor that uses tree sitter syntax highlighting. Okay, so that's it's just adding custom rules so that if you hit any of these things >> well maybe maybe it will be easier to write like I don't know if I could write that though but somebody did **[42:40]** >> somebody did hey you know what I'm going to also link a post in the show notes here or at least I'll give you a you know tell you right now to check this thing out z.dev dev blog text manipulation text manipulation kung fu for the aspiring black belt. This thing should give you some ideas about the commands and things that exist that we didn't talk about. Like this is how I learned about uh the convert case prompt just existing. And what they do is they give you a number of challenges to you know move line, select all matches, **[43:10]** convert case uh being able to do so in a fast way. This was a really cool blog post. You know, how to review multicursors um with keyboard commands. You're setting up all these multicursors at once. There's a lot of neat stuff inside of here. I also really appreciate that their example uses iconic kung fu actors. Um got to love that. These are some great films, folks. Uh other than that, yeah, check this blog post out. Check out Zed. Let us know what you think. Are you been Have you been using **[43:40]** Zed? What do you think? What did we miss in this? Is there anything that we did not cover that you think is uh really much required uh knowledge about Zed? Again, it is a nicely performing editor. I I will say that, you know, we're used to and not all Electron apps are bad and VS Code is one of the better performing Electron apps, but there are times in VS Code where you get an extension that will just crush your computer. Like was that Wix's version there were version **[44:10]** package version plugin. Man, if you're still using that thing, get it off your system, man. It will just crush you GPU. >> Yeah. And now, especially everyone's got 500 MCP servers and agents running in the background as well. There was a time on this podcast where I said like, do will we even need more powerful computers than these MacBook M1s and and here we are a couple years later being like, I need like nine of these just to run all this crap out. >> No kidding. Just to all run all this crap. I know. I've moved to like a like **[44:41]** I I went from like a very maximalist setup where like Comet was eating up my RAM to I'm using now Helium browser which is like really nicely tuned to be really fast. Zed very fast, ghosty, very fast. >> It feels just feels good and it's it's a weird thing like if if there's any reason to use zed, it just feels good. And like I wouldn't say VS Code is >> slow, you know? People always talk about that with with Sublime. and they'd be like, "It's so slow." You're like, "How fast do do you need characters to show **[45:12]** up on the page, you know, and like how often?" Or they would show like opening up a 600 line file and it takes like 0.2 milliseconds to highlight the entire file. It's like how often are you opening new files and and waiting for the syntax highlighting? But then you I I often have this like I'll say like who needs more than 60 hertz and then you use it my new my new iPhone. I never said that. I'll be honest, folks. >> No, I know you're the opposite. You're always just like, "Yes, this is so good." But then I use it, I'm like, "Oh, **[45:43]** yeah. I understand this now." >> Yeah. 60 Hz, man. I can't imagine going back to uh 1994. >> Wait, what's your what is your monitor? 60 120. >> Which one? Which monitor? >> Your your main Apple display. The Apple Studio display has a refresh rate of 60 hertz. That makes sense. Most most monitors are unless you have some crazy gaming monitor. It's like 120. But there's something about on having the **[46:14]** phone being a higher refresh rate. It just feels so good. Yeah. Well, no. I for me it's just scrolling like when you you can read things as you're you're scrolling and on the on the old one, I couldn't read things as I was scrolling because it would be blurry. >> Yeah. Hey, I want a higher refresh rate monitor now. Time to get rid of this. Oh man, I just I just baited Scott into realizing he didn't have a uh 120 Hz monitor. >> Yes, he did. Let's get into sick pics **[46:44]** and shameless plugs. We don't need to do a shameless plug, but let's talk about sick pics. Wes, is there anything that you're finding to be particularly sick these days? >> Yes, I'm going to half shameless plug and half sick pick this. So, we just launched these in our merch store. Um, and this is a set of syntax key caps. And it comes with a solid gold. It's not actually solid gold. Um, vibe key, which is the shape of a tab. Um, and then it also comes with a hyper key, **[47:17]** which is black gold. It's these are like the pure metal. They're nice and heavy. Um, and then there is three just regular keys. uh one syntax one one that says ship it and one escape one. Um those are plastic. Those are not metal, but they feel really good. So it comes on this little clicky thing where you can just use it as a fidget or of course you can you can take them off and and put them on your actual mechanical keyboard. So, if you ever wanted a custom hyper key, a **[47:48]** custom vibe tab key for your monitor or for your keyboard, mechanical keyboard, or any of these custom syntax escape, ship it keys, grab it from our merch store. Go to syntax.fm, click on swag in the URL bar. >> Yeah, my kids been fidgeting with that thing. They love it. >> Yeah, it's I love it. I find it hard like I I have to move it away from myself when I'm recording cuz otherwise I'm just pushing it all the time. You can hear it in the the background. >> I've never been a fidget guy. Maybe I **[48:18]** Maybe I got to get fidgeting. I'm going to Well, I'm a fidgety person, but not like a fidget clicker kind of guy. >> I'm going to stick pick at my new water cooker. I've I had a 3 L Zoji Rushi uh water heater, water boiler for like 15 years. It like survived various dorm or not dorms, uh apartments and then houses and moves. And this thing was an absolute beast. And uh sadly, we did not take care of it as much as we could have **[48:49]** in terms of like flushing out minerals out of the water. And eventually the age just caught up to it, right? That the fact that this thing lasted so long and that I didn't take great care of it should tell you that these things last forever, especially if you take care of them. So, we took it upon ourselves to say, you know what? Let's upgrade. We're going 5 L. We got a 5 L water boiler from Zoji Rushi. It's like 2.95 at Amazon, but again, it will last forever, man. And what it does is it keeps your **[49:21]** water Yeah. keeps your water at a specific temperature all the time. And if it's 5 lers, it lasts forever. So, our kids use this for oatmeal in the morning. We use it for tea every day. And it's just like you got water set to 195. Anytime you want to push the button, you got it. No. Coming right up. Big fan of Oji Rushi as a brand overall, but man, this thing just rules. >> Is this a a countertop unit or does it go under the sink? >> Countertop unit. Yes, countertop unit. **[49:52]** We don't have a lot of stuff under counters and it it it is it looks kind of tall in the picture. Um, but it does fit underneath like cabinets and stuff. No problem. So, >> I've been looking at this because we have like a like a kettle, right? >> And we have so much crap on our counters and I'm always like, let's get rid of this. You know, there's there's people that put their toasters away every day, and we're not that family. >> I put the toaster away. You put the toaster away. I'm putting it away every day. I'm putting it away, right? Yeah. >> I ain't I ain't got time for that. And I **[50:22]** often think like even when I'm cooking where like we have a gas stove and it's it's not as fast as like an induction to boil water. >> Oh, yeah. >> So, I'm wondering like what if we just had and we drink a lot of tea. What if we had that under the sink and just came out through the countertops? How sick would that be? >> Yeah, >> just a little tap. >> Hot water tap. >> Yeah, I like that. Cool. >> We have a fancy neighbor who has one of those. They have They also have this. I I kid you not, they have two dishwashers. >> Oh, man. We Let me tell you, we just got **[50:54]** a new dishwasher >> and we are planning we're getting our countertops redone and when we get them redone, we're going to have two dishwashers. It makes so much sense. Yeah, >> we I I got four kids and like not every day you need two dishwashers, but like the amount of times where you need to like parallel process two things. Like you got multiple cores on your laptop. Why can't you have multiple dishwashers? >> We don't have any room for two dishwashers in our house. Like there there would be literally no place to put it. But like to me that's luxury, baby. Like give me save me who knows how you **[51:27]** know how much and and install a second dishwasher for me and I'll be like living like a king. That's for sure. >> That's That's such a flex. And like a dishwasher is not expensive. You can get like a nice dishwasher for >> the Bosch ones. Yeah, they last forever. Yes, >> that's what we just got. I'll sick pick that in a future thing. We'll talk about We'll do dishwasher talk. But >> my goal in life is to have two dishwashers. That would be >> ultimate flex and like ultimate >> just help yourself out >> when you grab too many. Everything goes in dishwasher in our house, you know. I **[51:58]** put everything in the dishwasher. I have no time for hand washing. >> Yeah. >> Let's talk about Let's talk about flex uh or not even a flex here. >> Life upgrade stainless steel pans. Stainless steel pans. They're harder to cook with, but you you could use metal utensils with them. You can toss them in the dishwasher. You don't have to worry about microlastics on them. And like, yeah, they take there's a learning curve to using them. Yeah, your eggs are going to stick if you're not doing the right things. You're not doing the water test in them. But man, stainless steel pans, **[52:31]** >> carbon steel, >> carbon steel family over here. I switched from cast iron to carbon steel like two years ago. >> Man, it's the best. You got to still season it. Um, every >> Okay. You don't got to do anything for stainless. >> Yeah. Yeah. Yeah. Yeah. >> You got to use Barkeeper's Friend to scrape off some of that stuff every now and then, but >> because they burn the whole pan every time you use it. Yeah. >> Every time. Yeah. Let me tell you, man. Eggs. Scrambled eggs. How you do it?