Tangent: I wish we could standardize real-time code sharing the same way we have with LSPs. It is sad that if you want to pair-program, both have to be using the same editor. It really makes more sense to have one standard format so that one person can use VSCode and another can use Vim or Zed. If you want to make it standard practice you have to enforce everyone to use the same editor, which sucks. Already at work s…
Isn't that what Floobits is? https://floobits.com/
Zed, a collaborative code editor, is now open source
561–570 of 642 posts
Re: Zed, a collaborative code editor, is now open source
#562Earlier quoted context omitted.
> I'd suggest that the people who make "full use" of vsc-over-ssh are satisfied with vscode, so it would be unwise to target the full featureset. Remote SSH + Dev Containers and their seamless integration (even stacking one on the other) are the only features that keep me using VS Code. I would love to see the full implementation of these in an editor as fast and light weight as Zed.
How exactly are these features present in your workflow? I honestly struggle to think of when I'd ever use this. Fwiw, I do a lot of infrastructure-as-code, full stack, and systems programming. I usually have a split screen (editor | terminal) or two terminals on the side, and exec into a container, or use devenv.sh. If I _really_ need to modify files in the container as I dev and a "make" doesn't cut it, I usually j…
Similarly, editing code in-place over SSH rather than rsyncing back and forwards is very useful for certain types of embedded development. I worked for a while on sensor systems where a lot of the logic was handled by a Python webserver that couldn't really run without access to the sensor data it was using. Developing entirely locally was therefore difficult, but developing on the machine was also painful because it didn't have the right tools. So we'd work locally, and then copy the Python files over every so often and restart the server. At the time, I don't think VSCode's remote stuff was working as well, but I believe now it's a lot better and could have handled that situation well - edit everything in-place, run it immediately, but still have the power of you local development machine available to you.
Re: Zed, a collaborative code editor, is now open source
#563Is there a way to explicitly disable Copilot/AI/collaboration features? I won't be able to use this at work if there's a risk that it'd upload my code. It looks like a very fast editor (with Vim keybindings!) and I'd love to use it even without AI :)
"copilot": {
"disabled_globs": [
".env"
]
}
I imagine * would work there too.I don't see a way to disable all the collaboration features, but it does look pretty difficult to do it by mistake. You have to add collaborators explicitly.
Re: Zed, a collaborative code editor, is now open source
#564Earlier quoted context omitted.
If you have to install plugins then it's not an IDE, it's just a text editor.
I wonder what you'd consider an IDE nowadays. Modern text editors do every single thing. Is it just about the installation format?
That's an outrageously false statement. If it were true, you'd rarely need plugins.
> I wonder what you'd consider an IDE nowadays.
The definition of an IDE hasn't changed in at least 20 years. INTEGRATED development environment.
If I install a C++ IDE, I have everything I need out of the box, and the experience is (usually) consistent across all features.
If I want to do C++ in Vim, I need to install about 10 plugins (to begin with) [1], which will result in a disjointed experience (each plugin has different authors with different visions) where things break randomly and I don't know why. Speaking from experience, unfortunately.
Yes, you can make it work and you can get used to it, but it's just a text editor that you try to coax into doing what you want by using plugins.
Whereas the IDE will give you a language-specific tool out of the box, without any significant effort or inconvenience on your part. And the overall experience is better because the IDE "just works" most of the time.
[1] https://stackoverflow.com/questions/4237817/configuring-vim-...
Re: Zed, a collaborative code editor, is now open source
#565Earlier quoted context omitted.
emacs. Totally free and open source since 1976. oh, sorry, you asked for an IDE and not an operating system... /s seriously, budget a day or two for the ergonomics and a week for wrangling plugins, but some of the most productive developers in the world use emacs and they never need to worry about vendor issues, porting issues, not having a GUI, support for some weird file type, ability to create some funky type of m…
I tried to get into emacs a few years ago and just got fed up with the incredible regularity with which packages broke during routine updates. It was at least an hour a week on average, I feel, conducting bug hunts for either minor (this or that keybind/function doesn't work) or major (I can't get any packages to load) bug hunts. Was I doing something wrong? How do emacs people deal with this? Admittedly, I was using…
Stockholm syndrome.
Re: Zed, a collaborative code editor, is now open source
#566Re: Zed, a collaborative code editor, is now open source
#567Earlier quoted context omitted.
I like CLAs. If there's an open source project that I love/depend on, I will most likely want to be able to contribute to it for my own personal reasons at some point (e.g. fix a bug that bothers me or add a feature I want). I am a Sublime Text addict, but hate how slow development is and how resistant they are to adding more dev-focused features. I would happily sign a CLA if it meant I could modify the code myself,…
You do not need to give anyone special permission to sell your contribution, everyone in the world is equally entitled to make commercial use of (including outright sale of) free and open source software; without this it is not free or open source. The only purpose of a CLA like this is to provide for a future where the software can be made non-free again.
Public domain is closer to “equally entitled”.
Re: Zed, a collaborative code editor, is now open source
#568I looked at some random files, did not find a single comment, very strange.
What a weird statement. It's beautiful! You don't need comments, just read the code. No need to litter code with ambiguous language. The only place a comment fits is if the purpose is not clear from the code.
Re: Zed, a collaborative code editor, is now open source
#569> GPL for the editor, AGPL for server-side components). GPUI, the UI framework that powers Zed, will be distributed under the Apache 2 license, so that you can use it to build high-performance desktop applications and distribute them under any license you choose Interesting choice on licenses. —- I’m been super happy with Zed, my main requests (and I’ve sent in this feedback to them or contributed to existing GitHub…
I love jetbrains because it’s so feature rich and helps me a ton but god damn it’s slow.
Re: Zed, a collaborative code editor, is now open source
#570Earlier quoted context omitted.
Most programmers I know prefer macOS above all other. Is it different where you’re from?
There are obviously more programmers on Linux and Windows than on Mac, no matter your bubble. Since zed is Mac only, necessarily most programmers won't use it
It's likely to be the case for the "bubble" of the Zed authors.