Earlier quoted context omitted.
It's a pretty decent editor to be fair. The AI features are probably there to raise money from investors.
If it's so decent why isn't there even a version for Windows....
Zed – The Editor for What's Next
51–54 of 54 posts
Re: Zed – The Editor for What's Next
#52I’ve been trying to love Zed for months now and still run into constant snags. It’s frustrating to use with TypeScript. Support is very intermittent as basic features randomly break and come back during the same session. Want to jump to a declaration? Maybe it’ll work. Want information about this type? If you’re lucky. How about autocomplete for existing types, variables, and functions? This probably breaks most ofte…
As a comparison, I write Rust as my main language, and the tooling always _just works_. The experience with Zed is very good. Maybe the time for Zed in TypeScript development is not yet there, but if you write any Rust code, it's worth a try.
Re: Zed – The Editor for What's Next
#53I’ve never got its python LSP to work as well as Pylance in VSCode. Once you start using Pylance for large codebases, even if it is slow and sometimes crashes, you cannot go back to coding without it. Go to Definition, and automatic argument hints are too useful to code without
As far as I know Pylance (unrelated to pypi's pylance) is python LSP with microsoft's proprietary extensions that you can use only with official microsoft products. btw, go to definition, argument hints can work without it just fine.
Re: Zed – The Editor for What's Next
#54Earlier quoted context omitted.
As far as I know Pylance (unrelated to pypi's pylance) is python LSP with microsoft's proprietary extensions that you can use only with official microsoft products. btw, go to definition, argument hints can work without it just fine.
I’ve not gotten it working properly in Zed though, have others managed to do so?