I will never understand how you go back from a very customized editor setup to the one with "reasonable defaults with little to no things to configure".
Great talk on this topic by TJ: Personal Development Environment: https://youtu.be/QMVIJhC9Veg
41–50 of 154 posts
I will never understand how you go back from a very customized editor setup to the one with "reasonable defaults with little to no things to configure".
Great talk on this topic by TJ: Personal Development Environment: https://youtu.be/QMVIJhC9Veg
Zed doesn't run in terminal, sadly. That's the one reason I actually did end up using vim, even if Gui editors are theoretically highly superior. It's always there in the terminal with me. So you know how it goes, you set up $awesome_ide on a separate screen or what have you; start messing in the terminal, and then for quick edits you grab vim anyway. And once you have the whole edit/test/edit/test loop going, well,…
I’ve been using Sublime Text for more than a decade and I gave Zed a try recently. I don’t have good reasons like the author, but I kinda wanted to see what the hype was about. I really liked everything about it including the much better LSP support and the base key map for Sublime Text was very close so I felt at home quickly. Then I tried actually writing code in my usual workflow and this is where things started t…
> my workflow consists of switching back and forth between a terminal window and an editor window. Same! I run neovim in tmux together with stuff I hack on. I switch beteen tmux windows with shift-arrows and it works so well. I run this full screen in Ghostty. No distractions. I try Zed and VSCode and I always come back to this setup. It works so well for me personally.
I have Ctrl+` set to switch focus between the editor and the terminal panes in VSCode, so I can toggle between them pretty easily as this is also my workflow
If anyone's wondering, here's what I have in my keybindings.json
{
"key": "ctrl+`",
"command": "workbench.action.terminal.focus"
},
{
"key": "ctrl+`",
"command": "workbench.action.focusActiveEditorGroup",
"when": "terminalFocus"
},this resonates with me. i've spent so much time configuring neovim in the terminal (kitty) and i've never had everything work 100% of the time. simple things just like seeing an entire typescript error are challenging to get working. those errors just continue on one line outside of the screen.
with LLM's the tradeoff tipped in the favor of cursor with the neovim extension.
> 2. It just works
so i switched to cursor last week from neovim in the terminal and this is how i feel. but, i'm not going to invest more time to check out Zed now that i just got cursor set up the way i like it.
but it's great to see all the progress in IDE's lately.
Also half my workspaces are on remote servers and Zed lets me switch between remote and local workspaces easy which I appreciate.
I switched just to keep things interesting and didn't go back. That was last year maybe Sep/Oct.
I had to use VSCode to collaborate and like it in general.
> my workflow consists of switching back and forth between a terminal window and an editor window. Same! I run neovim in tmux together with stuff I hack on. I switch beteen tmux windows with shift-arrows and it works so well. I run this full screen in Ghostty. No distractions. I try Zed and VSCode and I always come back to this setup. It works so well for me personally.
Yeah the tmux / vim combo is so hard for me to beat with other editors still. I used Zed exclusively last month thinking the LLM integrations would be a compelling enough reason to finally switch. Like the post author, I'm a little fatigued with config / plugin churn since I switch languages frequently and it always takes some customizing to make vim work well when I do that. As the author describes though, I found m…
I'm using Zed too. It is VS Code-ish but feels fast, works out of the box and feels just... right. I wish it had support for Jupyter notebooks, but it looks like it will get there. And it never crashed on me, unlike VSCode which reminds me of Windows 3.1.