5 ms·
This is the direction I expected things to go, and not something I'm especially fond of. I'll stick with UNIX-philosophy tools, thanks.
by zahlman 1y ago
This is the direction I expected things to go, and not something I'm especially fond of. I'll stick with UNIX-philosophy tools, thanks.
- zem 1y agothis is very much in line with the unix philosophy - it delegates formatting to ruff and simply provides a unified front end that calls out to the right specialized tool. think of it as a makefile.
- zahlman 1y agoI don't think this is an apt (pun intended?) comparison at all.
- d0mine 1y agoOne can find repos using `make format` / `make lint`/ `make typecheck` / or similar I remember David Beazley mentioning that code with Makefiles were relatively easier to analyze based on ~Terabyte of C++ code and no internet connection (pycon 2014) https://youtube.com/watch?v=RZ4Sn-Y7AP8 https://youtube.com/watch?v=RZ4Sn-Y7AP8
- Kwpolska 1y agoThat `make format` command was not defined by the Make developers, but by the team using Make in their project. They picked their favorite formatter and defined a shortcut. In this case, the uv developers are forcing the command on everyone, and they're using it to cross-promote their own formatting tool.
- Hendrikto 1y agoThey are not forcing anything on anyone. You can decide to never run `uv format` and ruff won’t even be installed. You can use uv without ruff. You can use ruff without uv. You can invoke ruff yourself if that’s what you want. Or use any other formatter. I don’t think I understand what your complaint is.
- wiseowise 1y agoNobody is forcing you to use anything. Feel free to ignore it and use whatever flavor you like.
- asa400 1y agoOther people having an opinion and creating their own software project to implement it is not “forcing” anyone to do anything. The inverse would be no one is allowed to create any projects that you don’t personally agree with.
- zvr 1y agoA better example might be: in good ol' days when we were formatting with troff(1), passing arguments to the command line invoked other programs like eqn(1) and tbl(1).
- zelphirkalt 1y agoIf I want to call ruff, I can do so myself. Why should I want to call it through uv?
- woodruffw 1y agoIf you want to call ruff directly, this doesn't change anything. It's a purely optional feature. However, to answer the question generally: people want this for the same reason that most people call `cargo fmt` instead of running rustfmt[1] directly: it's a better developer experience, particularly if you don't already think of code formatting as an XY-type problem ("I want to format my code, and now I have to discover a formatter" versus "I want to format my code, and my tool already has that"). [1]: https://github.com/rust-lang/rustfmt https://github.com/rust-lang/rustfmt
- wiseowise 1y agoSome of us prefer well packaged tool that does everything instead of stitching together bazillions of dependencies.
- zelphirkalt 1y agoOr maybe some prefer random versions of dependencies being downloaded and running over our code?
- gchamonlive 1y agoThere is wisdom in knowing when -- and how -- to break standards. Don't know if this is the case, but I think it is. If introducing fmt powers to UV meant it had to consider tradeoffs elsewhere where it might hurt its quality somehow then maybe, but in this case UV is more like an umbrella, unifying the interface for pip, venv, builds... And now fmt. All keeping each separate domain isolated without details leaking to one another.
- zahlman 1y agoWhat do I gain from adding 'uv' to the start of each of these commands, as opposed to having them all just be separate commands?
- gchamonlive 1y agoI also don't know what I'd gain, but it doesn't mean there isn't practical use for someone else. But most importantly, apart from breaking away from "UNIX-philosophy tools", what do you lose in practical terms?
- asa400 1y agoAbstraction. Not having to know all the innards (or even names) of each until you want to. It's all there if you want to, but stuff like uv (or cargo, or go's toolset) greatly simplifies 3 scenarios in particular: starting a new project, joining an existing project, and learning Python for the first time. All 3 scenarios benefit from removing the choice of build tool, package manager, venv manager, formatter, linter, etc., and saying, "here, use this and get on with your life".
- zahlman 1y agoHow is "uv format" a better name, or more "abstract", etc. etc., than "ruff check"? Why is it easier to think of my formatter and package manager (or whatever other pieces) as being conceptually the same tool, given that they are doing clearly different, independent and unrelated things? And why is any of this relevant to first-time Python learners? (It's already a lot to ask that they have to understand version control at the same time that they're learning specific language syntax along with the general concept of a programming language....)
- smohare 1y ago[dead]
- cedws 1y agoI mean, Go was designed by one of the authors of UNIX, and that has very much batteries-included tooling.
- Kinrany 1y agoThe spirit of the unix philosophy is not implementing MxN use cases separately. Running the same program as a separate binary or as a subcommand has nothing to do with it