As a web developer that's an immediate deal breaker. I use Sublime today and being able to run multiple LSP servers per file is a huge boon, it turns a very capable text editor into a total powerhouse. The way it's set up in Sublime with configuration options that can be applied very broadly or very specifically, while having defaults that just works is also just incredible.
While I'm super pleased with Sublime and a happy paying customer since at least a decade, and at this rate may well be for another decase, I'm always keeping my ear to the ground for other editors if nothing else just to stay current. Zed's been looking pretty cool, but things like this will keep me from even just trying it. There's years of muscle memory and momentum built up in my editor choice, I'm not switching on whim.
Thank you very much for sharing this nugget of gold!
In my currently opened project I have: vtsls (for typescript), biome, emmet, and the snippets LSP running on the same file.
You can configure which LSPs you can run on a language basis. Globally and per project. You can also configure the format on save actions the same way. Globally and per project.
I have astro project that on save runs biome for the front-matter part followed by prettier for the rest.
I would say that's pretty flexible.
Does this work on anything other than VSCode ? I have been trying to use JetBrains stuff for this but it has been bad for years with little improvement. Honestly JetBrains feels like they are falling behind further and further in terms of adapting to providing a modern workflow - bad remote work, bad gen AI integration. I'm using VS code even where I wouldn't consider it before because of this, and I would like to see what the alternatives have to offer because VSCode is not perfect either.
This is supposedly temporary though IIRC (may even be changed already in a dev branch, not sure).
No, they aren't anything better than what I am used to.
Also, as compromise, a cloud shell, browser based IDE setup, and dev containers, also does the job in what concerns cloud deployments, which should be driven from CI/CD and don't have shells on containers anyway.
Remote VSCode is far better than any of those options. If you don't want to try it that's fine, but don't pretend you know better.
The ultimate deal breaker, however, is X11 not being proxied by corporate firewalls, even though the protocol is extensively documented and the source is available. But that is because RDP has won over, and demand for X11 has diminished.
But, yes, X11 prefers local networks with flat topologies, and the protocol is chatty (again, not as big of an issue anymore unless run over a mobile connection with a high latency, but the X11 protocol compression helps with that).
vscode's remote services is far beyond your old remote experience, an experience I share
Also, no support for debugging yet.
I also have no idea what kind of code people "write" that they can rely on A.I. so much. I have found these tools helpful for gathering info but not for much more, yet.
I also find Zed to be snappier than VS Code. It's hard to quantify but it just feels better to use Zed.
For reference, I mainly work on a Node/Typescript monorepo that is made up of a bunch of serverless services and is deployed with SST v2
A use case is Angular or other more specialized frameworks, that are so abstracted away and dumbed down that each layer of abstraction basically has an LSP.
Just try what people offer right now, at a price point that you are okay with, right now. In a year, both product and price will probably be moot.
Right now you can run multiple language servers in a single project. Admittedly you cannot have multiple instances of a single language server in a single worktree (e.g. two rust-analyzers) - I am working on that right now, as this is a common pain point for users with monorepos.
I would love to hear more about the problems you are having with running language servers in your projects. Is there any chance for us to speak on our community Discord or via onboarding call (which you can book via https://dub.sh/zed-c-onboarding)?
I still, for example, can't get Zed / LSP to provide auto-fix suggestions for missing imports. (Which seems like a common stumbling block: https://github.com/zed-industries/zed/discussions/13522, https://github.com/zed-extensions/java/issues/20, https://github.com/zed-industries/zed/discussions/13281)
I'm sure given the breadth of LSPs, that they all have their own config, and use different project config files, makes it hard to document clearly. But it's an area that I hope bubbles up the roadmap in due course.
The newer specs for json-schema (not supported by VSCode) allow for a wider range of data requirements to be supported by a schema without that schema resorting to costly workarounds. VSCode's level of support for this is decent, but is still a pain point as it creates a sort of artificial restriction on the layout of your data that you're able to have without unexpected development costs. This of course can lead to missed estimates and reduced morale.
I understand that very few developers are directly producing and maintaining schemas. Those schemas do have an impact on most developers though. I think this is a problem that is being sadly overlooked, and I hope you can consider changing the status quo.
Love the company name btw, sounds similar to my own Nuzz Industries (not a real company, just a tag I've slapped onto some projects occasionally as a homage to Page Industries from Deus Ex).
Samsung should be avoided like the plague anyway, I've never seen such a malicious and hostile company! On Dec 13 they silently announced that they were gonna break Samsung APIs on Dec 30 [2]. Yeah, they gave devs the "You gotta spend your holidays fixing our mess, otherwise your app will break". Due to that Samsung is still broken in Home Assistant and other API integrations. [3]
[1] https://youtu.be/a4NJNdHqs_I?t=418
[2] https://community.smartthings.com/t/changes-to-personal-acce...
I'm deeply interested in knowing why, if the answer is anything besides you have always or mostly used Samsung and are used to it.
I've avoided them for years. I had a Samsung phone a long time ago, and I'd rooted it to run one of those apps that could automate tasks (Tasker?), with a killer feature being when I turn my phone upside down, it goes on silent mode. Standard now, but back then wasn't possible on Android, and Tasker enabled it. And also some geofencing stuff. If I got a text while going faster than 10mph it would respond back "driving right now, will respond later."
Anyway, Samsung released an upgrade that I'd heard would eradicate root and make it impossible going forward. Something to do with Knox, a corporate way of locking down phones for employees.
I repeatedly declined to upgrade.
Finally, one night, with my phone in another room, it force-installed the update, with Knox, on my phone, wiping out my root, making it impossible going forward, and making Tasker worthless for me.
I've never given Samsung another cent. No company that will disobey me re my own property and will remotely hack my device and wipe out my content can be trusted, and that's essentially what they did.
For similar reasons, I've never given Sony any money since the rootkit scandal. 2025 marks twenty years of no Sony. I've probably unknowingly seen a few Sony films, but that's it. No electronics, no games, etc.
Whether they change in 6 months or 24 months or 60 months is just a business decision of whether to trend towards continuous small increases or rare but larger jumps. The fundamental economic pressures that lead to higher prices in the long run are no different.
Only barrier for some folks will be if they're not familiar with rust or local LLMs in general, but it really wasn't that difficult looking back on it. Amounted to about an afternoon's worth of work.
To get custom tab completions working you need to mimic one of the completion provider apis (like copilot) [1] and direct the requests to your own endpoint. In my case, I am running llama.cpp and and MITM-proxying to its newer /infill endpoint [2]
That's why I mention the rust piece may be a blocker for some, you do have to hack apart the src a bit to get things working. At the time I started this, the only two completion providers available were supermaven [3] and copilot. You could mimic either.
[1] https://github.com/zed-industries/zed/tree/be830742439f531e8...
[2] https://github.com/ggerganov/llama.cpp/blob/master/examples/...
[3] https://github.com/zed-industries/zed/tree/be830742439f531e8...
Branch is a bit out of date vs main now but it should work if you build off it.
There are a couple of MITM proxies I've seen for this purpose, the first of which seems to be maintained: - https://github.com/bernardo-bruning/ollama-copilot/tree/mast... - https://github.com/jjleng/copilot-proxy
When I tried a few weeks back I was only able to get the latter to actually process requests, but haven't had a chance to look into it much further yet... first one's probably your best bet
Common features like completions, diagnostics, and auto-formatting will multiplex to all of the LSPs.
Admittedly, there are certain features that currently only use one LSP: inlay hints and document highlights are examples. For which LSP features is multi-server support important to you? It shouldn't be too hard to generalize.
(not arguing)
recently saw an old alfred hitchcock presents where the character does the cheesiest most absurd rug pull ... and the person was boom dead. i assumed that was the origin of the term
OP edited to the idiomatic 'rug pulled from under my feet' to specify that he doesn't mean the above.
They are specifically hoping you'll become dependent on it and then feel compelled to pay. This shit works because people like you believe it doesn't.
Because they haven't decided the price yet, or because they don't think the feature is mature enough to justify charging for?
Though even if they really have the motivations you describe, that's fine too. There's a chance this is such a valuable feature you could feel compelled to pay any price for it, but you get to try it for free? That's purely to your benefit: it's not heroin and you won't really lose by trying it and then it being taken away.
> Q: Will Zed be free?
> A: Yes. Zed will be free to use as a standalone editor. We will instead charge a subscription for optional features targeting teams and collaboration. See "how will you make money?".
> Q: How will you make money?
> A: We envision Zed as a free-to-use editor, supplemented by subscription-based, optional network features, such as:
- Channels and calls
- Chat
- Channel notes
We plan to offer our collaboration features to open source teams, free of charge.
It seems to me that they're just going to charge for Zeta if they do, because it... costs them money to run.Unlike others (e.g. Cursor), they've opened it (and its fine-tuning dataset!), so you can just run it yourself if you want to bear the costs...
They did something similar with LLM use, where for simplicity they gave you LLM use, but you could use them directly too.
I love Zed, and I'm happy to pay for AI stuff, but I won't be using this until they are done with their rug pull. Once I know how much it costs, I can decide if I want to try integrating it into my workflow. Only THEN will I want to try it, and would be interested in a limited free trial, even just 24 hours.
Considering I've seen products like this range from free to hundreds of dollars per month, I'd rather not find out how good it is and then find out I can't afford it.
Other than that for anyone wanting to try Zed:
- You can only run one LSP per file type, so your Rust will work fine, your C++, too, your Angular will not.
- Remote editing does not work on Windows (its not implemented at all), so if you are on windows, you cannot ssh into anything with the editor remote editing feature. This means you cannot use your PC as a thin client to the actual chunky big work machine like you can with vscode. I've seen a PR that adds windows ssh support, but it looked very stale.