I lost all faith and interest in Zed after they introduced AI features.
The AI features work well but to each their own
Zed is our office
91–100 of 343 posts
Re: Zed is our office
#92I lost all faith and interest in Zed after they introduced AI features.
I feel the opposite way, but fwiw you can turn off all AI features in Zed by adding `"disable_ai": true` to your settings.json.
Re: Zed is our office
#93Earlier quoted context omitted.
Pair programming can be really great. Or horrible. Depends entirely on the people. This would be good for code-walks too though. Instead of having to share your screen and hope the video comes through well. Everyone can follow along in the comfort of their own editor.
> code-walks it's probably subjective, but I find these collaboration features can be overused for this kind of thing. If someone is walking me through something, I just want to see what they see so I can focus entirely on what they're saying and no part of me is distracted by having to follow along or seeing other code. I know typically these collab modes have an auto follow feature, but it's not as simple as just r…
Problem is video is expensive and compression can get bad.
I agree being able to see the pointer is important, since not everyone is good about moving the cursor around.
Re: Zed is our office
#94Technically really impressive. In practice, completely unpractical in any medium to large organization. And although I adore Zed's speed and reliability, I still don't understand why we need these features at all.
Because Zed is not somebody's side project, it's a business looking for ways to pay everybody's salary
> Collaboration as it stands today is considered alpha, and for the time being, is free for all to use! Peruse the source code.
Re: Zed is our office
#95Earlier quoted context omitted.
It could be easier, but it is supported AFAIK: https://github.com/zed-industries/zed/issues/8260#issuecomme...
Unfortunately, we no longer support self hosting. We're planning on reintroducing it once we've polished the single player experience a bit more :)
Oh, that's unfortunate. Why not support it at all, even if just for people who are kinda hacking it in?
Re: Zed is our office
#96I really really don't want comms or multiplayer tools in my IDE.
Don't bring the attention economy to my cave of solitude, it's where I go to escape all that noise
Re: Zed is our office
#97commence feature creep
Many of these features were in Zed since first release.
Also Zed was announced as a closed source comercial tool.
Re: Zed is our office
#98> Despite attempts to make Atom—an Electron application—more responsive, it never reached the performance standards the team yearned for.
This feels like an attempt at deflecting blame. VSCode is another Electron application that ended up having better performance than Atom. There's another Electron adjacent application that has good performance, the one you're probably using right now to read this page.
Depending on page content of course
Re: Zed is our office
#99I like Zed. I pay for pro. I like the integrated agent stuff (though my usage model has changed a bit after 5 months of use).
I'm happy that others can type in each others' space, but this post reveals a tension here. They are building a tool for building the tool, and their own team. I think that's cool, but at a 2-3 person shop heavy polyglotted across 4 OSes and 5+ programming languages, this is not what I really need.
What I'm looking for is a snappy tool (check) that lets me explore, understand, modify code at a next level (marginal). And I want it to not only be snappy by virtue of execution efficiency, but cognitive load. I want the less-is-more experience. I don't need it to do Swift, Kotlin, or Python, because there are bespoke IDEs for each of those that focus on the environments where I deploy them best. What I mostly want from Zed is the ability to see the outline panel at the same time as the directory panel, and to separate the search outline from the file structure outline. I spent too much time toggling views in Zed.
Re: Zed is our office
#100Zed is lovely and I hope it becomes super successful but this kind of mass collaboration might be ok for meeting minutes... maybe. But thinking of it for coding it gives me shingles. Code by mass live committee. Yikes.
> Code by mass live committee. Yikes.
Let's lean into the chaos and see what it might give us. Imagine a production application deployed directly from a non-version-controlled directory. Anyone on the team can edit the files, at any time. Insane? Probably. The disadvantages are easy to see.
But the positives are really compelling: 1. make small, granular testable changes; 2. use feature toggles; 3. refactor intensely and concurrently; 4. always work on the latest code; 5. use in-code documentation instead of GitHub/etc workflows; 6. explore continuous, incremental, hot-swappable code deployment.
Doesn't thought of ditching all the wasted motion and ceremony around logging async work and just coding sound glorious? I'm actually not a "move fast and break things person" usually. But the idea of moving so fast that broken things will only stay broken for a tiny fraction of the time is pretty compelling. There is also an intensity that comes from real-time interactions where a team needs to reach consensus quickly.
Feature Toggles: https://martinfowler.com/articles/feature-toggles.html
BEAM (Erlang, Elixir) provides hot-swappable code and lots more