Their custom UI framework might be all fun and games for now, but that will probably change once they realize they need to implement accessibility. Doing this in a custom framework without sacrificing performance won't be easy and is going to require lots of messy, per-platform work. It's not like it's optional for them either. It would be for a simple editor that you can just decide not to use, but they're positioni…
[flagged]
We Have to Start Over: From Atom to Zed
111–120 of 243 posts
Re: We Have to Start Over: From Atom to Zed
#112Earlier quoted context omitted.
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.
I don’t believe there’s a useful distinction, at least for more advanced editors. For instance, I’m not aware of anything you can do in, say, PyCharm that you can’t do in Emacs or Vim. I don’t mean that in a curmudgeonly way like “nothing I care about, because we don’t need those fancy features to write a pageful of Fortran on my 1997 laptop”. I mean, I don’t know of a single feature of any kind that doesn’t exist on…
All composed commands. Like Repeat. As in `repeat the following command 5 times`.
Like `d5` in Vim (delete 5lines).
Or y30 (Copy 30 lines).
Or `V?^func` (select text from current cursor position to the beginning of the function).
None of those are memorised commands. They're simply one command composed with another.
Composability is the real killer feature in Vim. Even in Emacs, I don't get the same ease of composability as I do in Vim.
Re: We Have to Start Over: From Atom to Zed
#113Re: We Have to Start Over: From Atom to Zed
#114Their custom UI framework might be all fun and games for now, but that will probably change once they realize they need to implement accessibility. Doing this in a custom framework without sacrificing performance won't be easy and is going to require lots of messy, per-platform work. It's not like it's optional for them either. It would be for a simple editor that you can just decide not to use, but they're positioni…
[flagged]
Re: We Have to Start Over: From Atom to Zed
#115Earlier quoted context omitted.
Logically it doesn’t, but in actual good-faith communication people usually follow Grice’s relevance maxim[1]: the points they mention are relevant to the conversation and the point they’re making. Thus, if neither Linux nor Windows support are planned, and the question is about Windows support, saying that Windows will come after Linux would be (vacuously) true, but the mention of Linux would be irrelevant. (Notably…
Hey! I'm the mentioned Thorsten. Linux is actively being developed. Here's a PR from 2 days ago that shows file-opening in Linux starting to work: https://github.com/zed-industries/zed/pull/7852 And so far Linux support has been a big community effort. I think more community member contributed to Linux support than Zed teammates. Very cool to see. So: Linux is in the works. Windows will probably happen after that, or…
Re: We Have to Start Over: From Atom to Zed
#116Had 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.
In my opinion I wish more editors would become a face to Neovim which can run in a headless mode, allowing you to not have to emulate VIM at all, but take full advantage of it and all its plugins. It still kills me JetBrians chooses to maintain what VIM users call an awful plugin that simulates VIM, when they could just implement a Neovim front-end natively into their IDE, giving them the edge of "we fully support Ne…
I'm thinking it would be nice if my Lazarus IDE supported Vim commands.
Re: We Have to Start Over: From Atom to Zed
#117Earlier quoted context omitted.
I didn't get it at first, but as I read it the last "Zed" is not the editor but the company. Basically the Zed company also gets access to the code you're sharing with other users.
In other words, “when you use our servers your data will be on our servers but we’ll only access it when we’re debugging our servers.”
Re: We Have to Start Over: From Atom to Zed
#118Their custom UI framework might be all fun and games for now, but that will probably change once they realize they need to implement accessibility. Doing this in a custom framework without sacrificing performance won't be easy and is going to require lots of messy, per-platform work. It's not like it's optional for them either. It would be for a simple editor that you can just decide not to use, but they're positioni…
[flagged]
Re: We Have to Start Over: From Atom to Zed
#119Earlier quoted context omitted.
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…
VSCode came out of nowhere and took the market share previously held by Atom and Sublime Text 2 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.
Re: We Have to Start Over: From Atom to Zed
#120Earlier quoted context omitted.
[flagged]
They’ve only spent 10 years writing text editors. They might not have heard of accessibility before. /s