5 ms·
Why is "written in Rust" a feature to be mentioned? Who cares? So my type checker has memory protection and is compiled. I'm not running my type checker on an
by doug_durham 1y ago
Why is "written in Rust" a feature to be mentioned? Who cares? So my type checker has memory protection and is compiled. I'm not running my type checker on an embedded system or in a mission critical service. It seems kind of like "written in Erlang". I'd prefer to have non-performance critical code for Python written in Python. That way the broader community can support and extend it.
- tomrod 1y agoShortcut for "noticeably fast." Open source Rust is still review able.
- beeb 1y agoIt makes it easy to find performant and quality software by searching for "[insert tool description] rust", I personally don't mind! Seeing how 95% of the tools I use on the daily are written in Rust, I love finding new ones and am rarely disappointed.
- mcbuilder 1y agoI feel like 70% of open source projects on GitHub say written in the language that they were written in
- bpshaver 1y agoI feel like the likelihood that a project will say what language it is written in is much higher if that language is Rust. I like Rust but I do find this trend a little annoying. (Even though I acknowledge that "written in Rust" probably means the tool is relatively new, not buggy, and easy to use.)
- lynndotpy 1y agoHave you used Rust before? As a user, the speed and safety is nice. But as a developer, Rust projects are easier to hack on and contribute to. That's kind of the whole appeal of Astral. I know Python better than Rust, but it's a lot easier for me to hack on Rust projects. The whole appeal of Astral is that they want to bring Rust-quality tooling to Python.
- mdaniel 1y ago> but it's a lot easier for me to hack on Rust projects That static typing is nice, I wonder if it's going to catch on one day. The amount of energy spent trying to bend dynamically types languages into being real ones is just comical. Even the standard library is barely typed, so they give no fucks https://github.com/python/cpython/blob/v3.13.3/Lib/re/__init__.py#L164 https://github.com/python/cpython/blob/v3.13.3/Lib/re/__init... What does it accept? Who knows. What does it return? Don't worry about it
- lynndotpy 1y agoStatic typing is a big one, but I've been so steeped in Python that I don't appreciate it as much as maybe I should. The big thing for me is that most Rust projects are statically(ish) compiled (like go) and only need a `cargo build`. No venvs or pip commands or node/npm/nvm or make, etc.
- mdaniel 1y agoAlso, the Zen of Python is supposed to be one obvious way to do something but ddg "python dependency manager" and have a good laugh. That actually becomes triple lol for when uv steps in and says "uh, your pip requirements.txt is unsatisifyable, what are you even?!" And let me just say what an absolutely stellar job the rustc authors have done with the error messages. Just out of this world thoughtful. I have not yet gotten on board with their compile time vs safety and insight tradeoff, but I can see why they chose those two axes
- misnome 1y ago
- dist-epoch 1y ago> I'd prefer to have non-performance critical code for Python written in Python A type checker is performance critical code. You can watch how Pylint, just a linter, written in Python, lints your source code line by line. It's so slow it can take 30 seconds to update the linting after you change some lines.
- misnome 1y agoOr entire projects abandoning checking because mypy is so damned slow for anything non-trivial
- mixmastamyk 1y agoMany of these make the mistake of running against an entire codebase instead of checking vcs first and only running against changed files.
- maleldil 1y agoYou still need to type-check files that weren't changed if they were affected by a file that was.
- nine_k 1y agoAn LSP is performance-critical code. It directly affects responsiveness of your IDE, or even the viable scope of a project that the LSP can handle. Rust is both CPU- and memory-efficient, quite unlike Python. (It could have been OCaml / Reason, or Haskell, they are both reasonably fast and efficient, and very convenient to write stuff like typecheckers in. But the circle of possible contributors would be much narrower.)
- maleldil 1y agoTo be fair, pyright's performance as an LSP is tolerable. The main issue to me is running the type checker as a pre-commit hook or as part of CI. Mypy is awful, though.
- yawaramin 1y agoThe circle of possible contributors doesn't really matter. It's a Meta project, they have others written in OCaml and to this day they manage to have contributors eg https://github.com/facebook/flow https://github.com/facebook/flow because they hire and pay them.
- smitty1e 1y ago> Why is "written in Rust" a feature to be mentioned? Who cares? If one is a "purist", the idea of non-python tool involvement may dissatisfy. Scare-quoting "purist", given the general lack thereof anywhere in Open Source, python itself being a case in point.
- deleted 1y ago[deleted]
- fastasucan 1y ago>Why is "written in Rust" a feature to be mentioned? Who cares? A lot of people. Correct or not, I think "written in rust" have become synonymous with "very much faster than the alrernatives" in the pyrhon community.