I have not looked at the source for 80-90% of the python packages I've used. if a tool is well-maintained, I don't care about its language if implementation. while I agree with the caveats you suddenly introduced in your last sentence, none of them apply to any of the tools you initially mentioned (uv, ruff, pyright) so I think you're actually arguing two different things and don't want to be convinced otherwise.

I think there's two perspectives here: one as a potential contributor, and one as a "simple" user.

as a potential contributor, sure, the language of the tool matters. something breaks and you go investigate the source files to figure out why and maybe open a PR. In that case, a different tech stack is no good - you'll have to learn a totally new language!

however as just an end user, I see no problem with something being written in whatever language. regardless of the implementation, all I do is open GitHub and file a new issue (if that). I don't care about whatever stack is being used, I never even look at it.

so it depends on your approach to your own usage pattern. aside from those options, I would expect any sufficiently well-designed tool to not require me to understand language of implementation to know why some particular invocation didn't work. and of course in the ideal world, if you use it and it works perfectly, then the question is immaterial anyway.

was this taken down? website connection times out, and is "excluded" from the way back machine

edit: found it archived from here (I'm not really sure what to think about this response article tbh) https://blenderdumbass.org/articles/Is_The_DeVault_Report_a_Spiteful_Metajoke

archived report: https://dmpwn.info/

just to add to the other answers - no need to have them in your home dir (that sounds like it would suck). use a tool like uv tool or pipx , or just manually create any venv you need under a path you choose, say $HOME/.cache/venvs/

uv actually does have a reimplementation of pipx, via uv tool or uvx: https://docs.astral.sh/uv/concepts/tools/#tools

the concept in the OP is different; it's an implementation of pep722 https://peps.python.org/pep-0722/

he wasn't actively wearing/using the ring while in the shire iirc

sadly no; position of hint is determined by the LSP server.

you could use this plugin (now archived) which was the way many people used hints pre-0.10:

https://github.com/lvimuser/lsp-inlayhints.nvim

https://twitter.com/DanyX23/status/1778045930291319268?t=uJUg0IG4KOrDR-_FHqwTSA

i was initially worried that this would be just another tool, but it actually looks like a pretty interesting and ergonomic take at a wrapper for common python dependency management workflow. excited to try it out

this article suggests shell allowed, but git also has a built-in feature for aliases itself. I prefer these as it allows you to keep using the git command normally (more consistent when you tend to use history search/auto-suggestions heavily).

running git config --global alias.st status, for example, will allow you to run git st as an alias for typing out the full git status (you can also manually add aliases to your ~/.gitconfig).

explanation here, it wasn't just for the meme: https://github.com/fish-shell/fish-shell/pull/9512#issuecomment-1410820102

It definitely would be. Next time someone posts a kernel written in Perl I hope they specify that.