Hacker News Reader

Comment by vovavili | Hacker News Reader

Projects that use ty for its type checking but something else than uv for managing dependencies are probably in a very tiny minority of users.

View on HN

but there's probably lots of projects that use uv, but not ty.

I'd imagine that, for a substantial percentage of these, part of it is to avoid negotiating and bargaining over an additional tool in your CI arsenal, especially in bigger corporate environments where these sort of conversations are dragged through layers of non-technical middle management.

Ty isn't a compelling option. If you want support for dynamic libraries, mypy is king. If you want speed and strict conformance, Pyrefly and Zuban are better.

Ty's original pitch was that it would have strong inference and be useful for gradually typing existing, untyped codebases, but AI made that moot. Adding types to existing code is now trivial.

>If you want speed and strict conformance, Pyrefly and Zuban are better

Not sure if that's true.

Pyrefly and Zuban are faster. Pyrefly and Zuban use less memory. Pyrefly and Zuban score higher on the type system conformance test.

Use whatever tools you want, but don't kid yourself. There's a reason Google adopted Pyrefly.

Where is your evidence?

I think part of ty's pitch is also that it's very simple to set up. I think only Pyright compares in this regard. I tried Pyrefly once and recall it being a bit more involved to start using.

They're all CLI tools and they all support LSP. The only setup advantage here is Pylance's, by virtue of shipping with VS Code. Other tools take two clicks to enable, plus or minus typing the tool's name into a search bar.

And the article says it won’t be automatically installed, so it’s only there for people that want it.

Reply on news.ycombinator.com