Hacker News Reader

Not yet tbh. I would realistically expect at least a year or more before you can expect any kind of parity with eg; pyright/basedpyright. Type checkers are hard and have a long tail of functionality that must be implemented.

ty is definitely not ready to be a pyright replacement yet. But it is usable as an LSP for simple things like go to definition, and deeper LSP features are on the roadmap for the eventual beta and GA releases.

https://github.com/astral-sh/ty/blob/main/docs/README.md#oth...

What's the plan for ruff? Will it be part of ty one day?

The current plan is that they will remain separate tools, but will work together nicely if you are using both. For instance, we want to add type-aware and multi-file lints to ruff at some point down the line.

What kind of codebases cause performance problems?

I've been using pyright with neovim for years and have never experienced any kind of noticeable lag.