Should bring some interesting new features to Zed quickly. Glad to see it.
Sequoia backs Zed
121–130 of 346 posts
Re: Sequoia backs Zed
#122deltadb sounds interesting. AI editors should look into letting you operate on multiple git branches simultaneously, like isolated browser tabs where the AI gen doesn't contaminate the other. One of the reasons I find LLMs don't increase productivity much is that I can't switch branches to multitask while it's processing. Context switching isn't always useful but there's still lots of opportunities for rapidly experi…
I have been running multiple instances of the Codex CLI tool in several terminals to do different stuff. You can even checkout the repo several times, write the todo to a file (or ask the agent to do so), if you need.
Re: Sequoia backs Zed
#123While i am sure this sounds insane i had to drop zed due to lack of the “last file dif” button gitlens vscode plugin provides.
It is a godsend on quickly debugging the why of things. If anyone knows how to replicate the same functionality with the same number of clicks in zed, id happily switch back to it.
Re: Sequoia backs Zed
#124Earlier quoted context omitted.
It's apparently this but I can't really say that I get it: https://bablr.org He seems to be saying he spent $350k making this. I guess it's some tooling for writing parsers. He has this to say about Zed: > Zed: Founded by Atom’s dev team, Zed was the rewrite that Atom always wanted to be able to do but couldn’t when Microsoft bought Github and made the executive decision to kill a product it might otherwise have had…
Haha yes I wrote that, thank you for sharing. We're approaching the problem by drawing from browser design. We want to see an editor with a DOM API for code documents. BABLR is a parser framework meant as a direct answer to Tree-sitter.
Myself and most people I know that switch to Zed (many from Sublime) did it because we DON'T want a DOM in our text editor. Webtech makes for crappy text editors.
Re: Sequoia backs Zed
#125I love the spirit of Zed. From the principles to the low-level implementation details, it all screams "good taste". It's immensely interesting as an object of study (the code is great, from GPUI all the way up). Having said that, I don't think an editor should be VC backed. It's the obvious pragmatic choice to get a team together to support a thing, but I'm concerned by it.
Sublime Text solved this 17 years ago with the 40-year-old shareware model. It's also faster than Zed, works on Linux/Win/MacOS, and is decently customizable.
There was a time around ST2 when it felt like everyone was using it and it could've become The Editor, then something happened and it's been left in the dust. I wasn't even aware but apparently even fourth version of ST was released, and that was in 2021.
I lost track of what happened there (moved to Vim back then), was it VSCode that killed it?
Re: Sequoia backs Zed
#126Earlier quoted context omitted.
I might HAVE to learn EMacs (prefer over Vim) because I think eventually everything else will be tainted by mandatory AI features and/or subscriptions.
Nothing against emacs, but check out NeoVIM. If you like Emacs, you might like NeoVIM and its powerful extensibility features.
What makes NeoVIM emacs-like?
Re: Sequoia backs Zed
#127Earlier quoted context omitted.
Sublime Text solved this 17 years ago with the 40-year-old shareware model. It's also faster than Zed, works on Linux/Win/MacOS, and is decently customizable.
There was a time around ST2 when it felt like everyone was using it and it could've become The Editor, then something happened and it's been left in the dust. I wasn't even aware but apparently even fourth version of ST was released, and that was in 2021. I lost track of what happened there (moved to Vim back then), was it VSCode that killed it?
[deleted]
Re: Sequoia backs Zed
#128Earlier quoted context omitted.
Sublime Text solved this 17 years ago with the 40-year-old shareware model. It's also faster than Zed, works on Linux/Win/MacOS, and is decently customizable.
There was a time around ST2 when it felt like everyone was using it and it could've become The Editor, then something happened and it's been left in the dust. I wasn't even aware but apparently even fourth version of ST was released, and that was in 2021. I lost track of what happened there (moved to Vim back then), was it VSCode that killed it?
Yeah Atom and then VSCode killed it. Turns out being able to use JS to extend your editor is quite valuable. Essentially every JS devs have their own Emacs without having to learn Emacs and Lisp
Re: Sequoia backs Zed
#129deltadb sounds interesting. AI editors should look into letting you operate on multiple git branches simultaneously, like isolated browser tabs where the AI gen doesn't contaminate the other. One of the reasons I find LLMs don't increase productivity much is that I can't switch branches to multitask while it's processing. Context switching isn't always useful but there's still lots of opportunities for rapidly experi…
> AI editors should look into letting you operate on multiple git branches simultaneously
Git worktrees are great for this. I built a little tool to make them more ergonomic: https://steveasleep.com/autowt/
You really don't need every LLM vendor to build their own version of worktrees.
Re: Sequoia backs Zed
#130Earlier quoted context omitted.
I might HAVE to learn EMacs (prefer over Vim) because I think eventually everything else will be tainted by mandatory AI features and/or subscriptions.
if you haven't checked neovim out, the Lua based config is really nice and easy to grok these days. 10x better than classic vimscript!
A year or two ago I moved away from one of the neovim distros when they randomly changed all the keybinds on an upgrade (such things really anger me) and set up my own config. Funnily enough, I preferred vimscript. I still do use lua of course for various things, but those just go in lua EOF blocks in the vimscript. Vimscript is really terse and convenient for many things, I love it.