I've never understood why HN has never included even a 80 character description. I think it would really help even if it was only shown on the comments tab.

One reason I could think of is because it encourages informative titles - I enjoy being able to click directly from home page to article, without having to look at the comments. A lower percentage of posters would explain Ruff in the title if there was a description. (Clearly it's currently not 100% either, that's why I'm here.)

Though this is something that keeps coming up on Reddit as well, I assume there's a reason why HN went with this design.

This conflicts with the HN guideline of not editorialising titles, which leads to titles often having little or zero context.

It’s clearly explained in the FAQ:

> How do I make a link in a text submission?

> You can't. This is to prevent people from submitting a link with their comments in a privileged position at the top of the page. If you want to submit a link with comments, just submit it, then add a regular comment.

If you want to add more context, add it in a comment. If it’s good people will upvote it.

It's a python linter, from what I've seen.

Implemented in rust, not python, so it's extremely fast. It's orders of magnitude faster than pylint itself.

How many orders of magnitude?

There's a very clear graph the first thing on ruff's GitHub page, easy to find and research yourself: https://github.com/charliermarsh/ruff Can't miss it if you take time to check out the project.

So 2, maybe 3

Your comment seems skeptical. Practically, It’s a night and day difference if you’ve integrated a linter with your editor. Plus, ruff is able to fix as well as lint.

Didn't mean it that way, something being 100+ times slower is a LOT. And I care a lot about tool speed. I just didn't really think I needed to be shamed for asking a question they had a ready answer for.

This would matter more if it did all the things Pylint does, but Ruff still has a ways to go. They're tracking progress in https://github.com/charliermarsh/ruff/issues/970.

Damm that's a lot of cases to cover. I wonder how performant will Ruff be once it reaches feature parity.

If you enjoy podcasts this episode discusses ruff: https://talkpython.fm/episodes/show/400/ruff-the-fast-rust-b...