231–240 of 642 posts
Earlier quoted context omitted.
Looking for collaborative editors in particular. Two people editing at once, on different computers. Each person has their own copy of the file, on disk.
I'm curious about your use case?
You know the AI craze is real when adding chat gpt-4 to a text editor is higher priority than Linux and/or Windows support
You should have a focus when you first build a product. You shouldn't be holding up your product progress because you don't support every platform.
This is the reason why you see a lot of apps support iOS before they release an Android app.
It better to build a good working app for one platform than to not build one at all because you are spending all your time supporting as many platform as possible.
Consider discarding the CLA if you anticipate third-party contributions. If you need to verify provenance, the Developer Certificate of Origin is a better approach. Otherwise, this (correctly) reads as a project which intends to take advantage of FOSS contributors for a while before pulling the rug and making it non-free again.
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, even if I end up paying to use my own code.
Giving the owner permission to sell my contribution (which is likely very minor compared to the rest of the project) gives me added peace of mind since I know that the project is (or can be) sustainable.
A rug pull is always bad, but it's not fair to assume that that's what will happen (unless you know something we don't).
And besides, even if it does happen, that's what forks are for. This project is licensed with GPL and AGPL.
Earlier quoted context omitted.
“Please don’t do it like a 4x4 truck, do it proper, like a bicycle” — there is some overlap between those things, but for people who are actually making full use of the former, the latter is not a useful suggestion
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. More generally, targeting another project's complete featureset is often a great way to get mired down in the wrong details. Unless you can afford to do a proper cleanroom -- then, you'll be able to at least match the performance and useful abstractions used in the original.
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.
> 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…
As you say the interface is elegant and distraction free by default, no twiddling required to get a happy place.
So far I've only used it for my personal projects and don't yet have full muscle memory, but weirdly even the keyboard shortcuts seem more intuitive.
Earlier quoted context omitted.
Hey! Engineer at Zed here. Linux port is on our roadmap. Hopefully we'll get it done this year!
Since you are here I'll hijack the thread :) What about remote support ala vscode-server over SSH.
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…