Live data from Hacker News

Zed, a collaborative code editor, is now open source

zed.dev

631–640 of 642 posts

Re: Zed, a collaborative code editor, is now open source

#631

Earlier quoted context omitted.

[flagged]

I don't think there's a way to talk yourself back up onto the horse here. Drive-by barbs like "worse than bad" are a plague on this site. It was a rude complaint about the website for an open source project, and it was called out civilly. Ironically, it's your personalizing response that skirts closest to incivility. You can just disagree next time (if you really want to) without lecturing people on empathy? I think…

You seem really choosy about whom you apply your empathy.

If I had chosen more direct words, and written my criticism with less emotion, then you clearly wouldn't have any issue with it.

My comment has 81 points at the time of writing this one. Clearly the majority opinion here is that the substance of it was worthwhile.

God forbid humans express emotion on the internet. You are welcome to criticize my expression. To simply filter it out as bad internet speak is, at the very least, a bad strategy.

Re: Zed, a collaborative code editor, is now open source

#632

Earlier quoted context omitted.

I don't think there's a way to talk yourself back up onto the horse here. Drive-by barbs like "worse than bad" are a plague on this site. It was a rude complaint about the website for an open source project, and it was called out civilly. Ironically, it's your personalizing response that skirts closest to incivility. You can just disagree next time (if you really want to) without lecturing people on empathy? I think…

You seem really choosy about whom you apply your empathy. If I had chosen more direct words, and written my criticism with less emotion, then you clearly wouldn't have any issue with it. My comment has 81 points at the time of writing this one. Clearly the majority opinion here is that the substance of it was worthwhile. God forbid humans express emotion on the internet. You are welcome to criticize my expression. To…

You used a tropey put-down. You couldn't even find an original way to dunk on the project. I have a lot of empathy to allocate this scenario, but it's unclear why any of it should go to you.

I don't mean to keep a flagged, unproductive subthread going, but since you're listening to me: stop writing that way on HN. Stop dunking on people's open source projects. Be careful with how you write criticism. The preceding commenter was absolutely right to call out the snark in that comment. If you don't call that stuff out, it spreads like kudzu, and pretty soon we're all just writing Youtube comments. They did you a favor, and you should thank them for it.

Re: Zed, a collaborative code editor, is now open source

#633

Earlier quoted context omitted.

You seem really choosy about whom you apply your empathy. If I had chosen more direct words, and written my criticism with less emotion, then you clearly wouldn't have any issue with it. My comment has 81 points at the time of writing this one. Clearly the majority opinion here is that the substance of it was worthwhile. God forbid humans express emotion on the internet. You are welcome to criticize my expression. To…

You used a tropey put-down. You couldn't even find an original way to dunk on the project. I have a lot of empathy to allocate this scenario, but it's unclear why any of it should go to you. I don't mean to keep a flagged, unproductive subthread going, but since you're listening to me: stop writing that way on HN. Stop dunking on people's open source projects. Be careful with how you write criticism. The preceding co…

You're the one dunking here.

Re: Zed, a collaborative code editor, is now open source

#634

Earlier quoted context omitted.

Not sure what Melvin is. I've always had issues, specifically when I have lots of packages, such as when installing stuff through lazy.vim.

Updating vim packages can be a nightmare if you don't vet your plugins and generally install stuff "just in case I want to try it out later". If you aren't using a plugin with any regularity, delete it.

Yeah but I never have issues with VSCode plugins, so I'm not sure what the difference is with Vim.

Re: Zed, a collaborative code editor, is now open source

#636
post #96

Earlier quoted context omitted.

I've never really pair programmed - I've worked on joint projects, of course, but collaboration occurs over discord/github. I'm intrigued - what does this actually consist of? Does one person write one function and another write the next while you chat about what needs to be done?

We tend to work on one 'thing' at a time. Sometimes that means we're both/all on the same few lines of code writing a new function - at which point one person is usually doing all or nearly all the typing. If you then need to go define a constant somewhere else in the code or something the other person does that so you don't have to pause. Other times one thing involves code in various places because you're doing som…

Thanks for elaborating, that sounds pretty fun.

Re: Zed, a collaborative code editor, is now open source

#638

Earlier quoted context omitted.

Updating vim packages can be a nightmare if you don't vet your plugins and generally install stuff "just in case I want to try it out later". If you aren't using a plugin with any regularity, delete it.

Yeah but I never have issues with VSCode plugins, so I'm not sure what the difference is with Vim.

I don't know what vscode's plugin architecture is like but I imagine it's just that Vim's is extremely powerful and, you know, with great power comes great responsibility and all that. Unfortunately, many vim plugin authors are not responsible, or don't realize they aren't being so.

Re: Zed, a collaborative code editor, is now open source

#639

Earlier quoted context omitted.

I think that is on the roadmap too, but possibly further down.

You know Windows is the most common development platform? If it were me I'd prioritize it

It is, but barely (windows is @ 61%, macOS is at 46% based on the numbers I found). And even if we ignore that, number of potential users is far from the only factor you’d consider when choosing the first platform to target for a new project. And then, ignoring that as well, just because an OS has more potential users in total, that doesn’t mean it has more potential users of your editor.

There’s lots of reasons to not choose windows as a first release platform, and it being ‘the most common development platform’ isn’t a compelling one, especially for a small team with finite resources.

Re: Zed, a collaborative code editor, is now open source

#640
post #604

Earlier quoted context omitted.

The Zed team disagrees. Here is what they say in the github discussion on the issue: ( https://github.com/zed-industries/zed/issues/5394 ) "We will let you know when windows support is under development. The Zed team isn't taking feedback on when we start on windows support, nor why we didn't start with windows. The amount of people on each platform isn't relevant, as it starts with the base assumption that more peop…

Haha, well they will get lots of feedback they don't want to take. A company like Jetbrains can do this to an extent due to existing products fueling long term R&D efforts before they bare fruit. Interested to see how this outlook holds up as the runway burns and investor pressure increases from that cool 12.5m they raised last year.

From what I can find, the used OS of software developers is 61% windows, 46% Mac so this argument has no weight on the considerations the team should make Å— it’s essentially a toss up.

Even if it weren’t a toss up and significantly more devs used windows, deciding to target windows based solely on OS market share is one of the worst things a small dev team with finite resources could do. It’s just not a compelling argument at all.

Post reply on HN