91–100 of 243 posts
Earlier quoted context omitted.
Or even worse, you own a Mac (say, through work), but aren't entirely in the Apple ecosystem and don't want to relearn everything and fight muscle memory every time you switch devices.
Remap the keys.
Earlier quoted context omitted.
it is actually faster and snappier to use on a beefy M2 max, on the same hardware zed starts up in half the time. the difference is very noticeable. of course it is much less configurable and doesn't work with a lot of things VS Code can do easily. edit: see this comment for a much better explanation than mine of what I originally meant https://news.ycombinator.com/item?id=39409763
Startup would have to be terrible for me to bother. VS Code starts in under a couple of seconds, and I have it open all day long; once open, other windows open even faster than that. If it took any longer than a couple of seconds, I'd start blaming the extensions other editors won't have.
Before anyone jumps on a new text editor band wagon, just a note on the license they have you agree to in using it: "Customer Data consisting of User content created while using the Solution is classified as "User Content". User Content is transmitted from Your environment only if You collaborate with other Zed users by electing to share a project in the Editor. [...]Zed's access to such User Content is limited to de…
I would like some commentary from you, sounds very reasonable to me, I don't understand what the problem is. Of course if you choose to share your project with others for collaboration, the content of that project is transmitted from your machine, what else would you expect? How would it work otherwise?
Basically the Zed company also gets access to the code you're sharing with other users.
Had a look at the About page, and the live coding feature does sound useful. I'm sure the guys are excited; it's a fun project. You get to write algorithms, optimise performance, and do GPU programming. But who needs another text editor that will probably never reach feature parity with Vim and a terminal multiplexer.
I would guess most developers do not use vim. Pretending that vim is the universally loved editor that every developer has agreed upon using seems pretty disconnected from the real world. VS Code came up out of nowhere pretty recently, and is used by a lot of people, so that shows that there is (or was, but still post-vim) opportunity for a new editor. Whether Zed is able to gain momentum to cater for the long-tail t…
The folks I know who use Emacs or vim (including me) are by and large still using those tools since before Atom and Sublime got popular. We just have LSP, now, like VSCode does.
Earlier quoted context omitted.
I feel like these classic editors are good to know just for general education like writing cursive. If you end up on some barebones system you will know how to edit a config file and exit. But for day-to-day it's all IDEs nowadays.
The line between "IDE" and "text editor" has blurred to the point where I'm not sure they're super useful terms anymore. When I used vim up till about 2019, I had it configured with all the toys to the point where it wasn't all that far off of where my VSCode setup is today. Also, you know, insert Emacs joke here assuming if you still have enough RAM to post, etc.
Earlier quoted context omitted.
I feel like these classic editors are good to know just for general education like writing cursive. If you end up on some barebones system you will know how to edit a config file and exit. But for day-to-day it's all IDEs nowadays.
The line between "IDE" and "text editor" has blurred to the point where I'm not sure they're super useful terms anymore. When I used vim up till about 2019, I had it configured with all the toys to the point where it wasn't all that far off of where my VSCode setup is today. Also, you know, insert Emacs joke here assuming if you still have enough RAM to post, etc.
The editor wars are over and everyone won because of separation of concerns. Yay!
Earlier quoted context omitted.
I actually prefer Mac only apps. It usually means the experience is way more polished.
compared to their non-mac versions?
There’s some talk in the Mac world about “Mac-assed Mac apps”. I use BBEdit as my main editor because it feels right. The default shortcuts are like every other Mac app. You can use standard Mac tools like AppleScript to automate it. It uses the same fonts, widgets, and menu systems as everything else. It’s made for that environment and it shows in a million ways.
VSCode is a marvel of engineering and I love that it exists. It also feels uncanny-valley “off” on my Mac in ways that make my brain itch, so I don’t use it. Same with Obsidian: it’s a brilliant app, but it bugs me. It’s not bad in any way, it’s just not the right choice for me.
Had a look at the About page, and the live coding feature does sound useful. I'm sure the guys are excited; it's a fun project. You get to write algorithms, optimise performance, and do GPU programming. But who needs another text editor that will probably never reach feature parity with Vim and a terminal multiplexer.
I would guess most developers do not use vim. Pretending that vim is the universally loved editor that every developer has agreed upon using seems pretty disconnected from the real world. VS Code came up out of nowhere pretty recently, and is used by a lot of people, so that shows that there is (or was, but still post-vim) opportunity for a new editor. Whether Zed is able to gain momentum to cater for the long-tail t…
[0] https://insights.stackoverflow.com/survey/2021#most-popular-...
Earlier quoted context omitted.
Startup would have to be terrible for me to bother. VS Code starts in under a couple of seconds, and I have it open all day long; once open, other windows open even faster than that. If it took any longer than a couple of seconds, I'd start blaming the extensions other editors won't have.
In a perfect world startup times would be indistinguishable from instantaneous.
If I'm opening a codebase with thousands of files, I don't mind to wait a couple of seconds, as long as it's responsive afterwards.
Earlier quoted context omitted.
Or even worse, you own a Mac (say, through work), but aren't entirely in the Apple ecosystem and don't want to relearn everything and fight muscle memory every time you switch devices.
Remap the keys.