RIIR VS ruff

It was, imo, inflated by the comments pointing to the RiiR sentiments, not the comments to that effect itself. Even repositories 'collecting' such instances (e.g. https://github.com/ansuz/RIIR) are largely not collections of making anyone to change their own software but just projects that happen to be written in Rust. (these out-of-scope issues are not being tagged appropriately). Overhyped controversy by all sides.

Dunno what news you have missed but there's entire internet brigades dedicated sorely to spam projects with "rewrite it in rust". There's even a repo documenting this.

The OP post in the link references https://transitiontech.ca/random/RIIR (Rewrite it in Rust) as a meme.

Yes, one can hope, but I wouldn't bet on it and I wouldn't suggest to RIIR. I don't want to be that person that pops up uncalled for and asks to Rewrite It In Rust. One might think "Oh it is just one additional issue to the ~2.2k already opened mypy issues" if they have at all realized that there are that many open issues.

It's died down a bit now, but there is/was a non-trivial amount of stupidity from Rust advocates whenever someone ran into a memory problem with C/C++ to "re-write it in rust" or to just rewrite things in general. (IE https://transitiontech.ca/random/RIIR)

Or even better, RIIR the Windows kernel!

What is it with people asking for rust rewrites of Xorg this week? https://github.com/ansuz/RIIR/issues/83

The second language is Rust, and I went with that partly because rewriting C in Rust is a meme in itself, and in part because it was much easier to think of how to nicely fix that bug in Rust than it was in C (just add a = to the range to be end-inclusive).

I think I mention this all the time when this comes up, but I learned the most 'best practices' through using ruff.

https://docs.astral.sh/ruff/

I just installed and enabled all the rules by setting

Ruff is a Python linter that helps to identify and remove code smells. Over 700 built-in rules: Ruff includes native re-implementations of popular Flake8 plugins, like flake8-bugbear. And also built-in caching to avoid re-analyzing unchanged files.

Because the Python's "ast" modules is too slow, and lacks proper "format" feature (it has unparse but it removes comments, and forgets the current style completely). I use "ruff" a lot (https://github.com/astral-sh/ruff) which is in Rust. But I want to be able to implement fast custom linters in Go (linters that ruff / fixit lack, and Python linters lack or are too slow).

I think it’s interesting that rye uses ruff (https://github.com/astral-sh/ruff) for linting and formatting. That’s the right call, and it’s also correct to bundle that in for an integrated dev experience.

I had to guess, that’s the path that the Astral team would take as well - expand ruff’s capabilities so it can do everything a Python developer needs. So the vision that Armin is describing here might be achieved by ruff eventually. They’d have an advantage that they’re not a single person maintenance team, but the disadvantage of needing to show a return to their investors.

Adding more weight to ease of setup and configurability, the choice came down on flake8. It is easy to integrate, since its also available through pip and let’s you configure which standards you want to omit by simply stating them as a list via the --ignore switch. Moving to ruff appears quite smooth, so future updates may do so.

I confess I stole the pip recipe from Charlie :D

https://github.com/astral-sh/ruff/blob/main/.github/workflow...

Ruff is an emerging tool in the Python ecosystem that describes itself as "an extremely fast Python linter and code formatter, written in Rust".