Exactly. I tried it, my first impression was "it's vscode with vim's speed". But sadly not enough vim for me. Given I dropped vscode because it was responding too slowly to my keystrokes, made it compelling at first glance.
One thing I do often is compare things using vim diff mode. The problem with diff'ing things like tcpdump's is there is noise (like timestamps that make similar things look different). In vim you can :diffthis them, use vim's regex commands to eliminate the differences, and bingo where it when off the rails becomes obvious. Vim can't diff two git revisions natively, but it's command line is powerful enough to let you write a shell script to do it. Or for something completely different, you want to edit / view an encrypted file, again it's possible to write a shell script that tells vim to hold the decrypted version in RAM only so it doesn't leak to disk.
I lost too much in the end so I'm back to vim, but it looks so promising. I hope it matures into something a little more flexible that is easy to script. The articles comments about using CPU and disk I/O when idle are also a little concerning.
FacelessJim · 23h ago
This site is unreadable on mobile. Too many nested bullet points
panstromek · 23h ago
Good point, I'll try to fix it. I'm not super satisfied with the current theme, but I haven't had much energy to go and find a better one.
panstromek · 22h ago
I reduced the nested indentation at least, that made it a bit more readable.
uaas · 23h ago
By early, I expected something early in relation to Zed itself.
panstromek · 23h ago
What would be a better formulation for what I mean (early in my journey)? I'm not a native speaker, so this title sounded correct to me.
uaas · 20h ago
Two weeks of using Zed, Zed after 2 weeks, First impressions of Zed, etc.
Exactly. I tried it, my first impression was "it's vscode with vim's speed". But sadly not enough vim for me. Given I dropped vscode because it was responding too slowly to my keystrokes, made it compelling at first glance.
One thing I do often is compare things using vim diff mode. The problem with diff'ing things like tcpdump's is there is noise (like timestamps that make similar things look different). In vim you can :diffthis them, use vim's regex commands to eliminate the differences, and bingo where it when off the rails becomes obvious. Vim can't diff two git revisions natively, but it's command line is powerful enough to let you write a shell script to do it. Or for something completely different, you want to edit / view an encrypted file, again it's possible to write a shell script that tells vim to hold the decrypted version in RAM only so it doesn't leak to disk.
I lost too much in the end so I'm back to vim, but it looks so promising. I hope it matures into something a little more flexible that is easy to script. The articles comments about using CPU and disk I/O when idle are also a little concerning.