The amount of pressure you feel telling you you are using too many tools should scale linearly with the number of tools you use. This discomfort you feel with seeing all of those config files is telling you something. Use fewer tools.
[deleted]
The creeping scourge of tooling config files in project root directories
61–70 of 214 posts
Re: The creeping scourge of tooling config files in project root directories
#62Also, please don't use dotfiles. There is no reason to hide such important files.
It's nothing to do with importance and everything to do with how often you need to see and access the file.
My .vimrc and .bashrc are super important, but I rarely need to edit them and I never need to be reminded of their existence, so having them show up every time I ran ls in home would be annoying.
Re: The creeping scourge of tooling config files in project root directories
#63Also, please don't use dotfiles. There is no reason to hide such important files.
On which systems are they hidden? I hadn't even considered this issue because no file browser I've used in the last ~10 years has hidden dotfiles. Maybe Windows Explorer does, but that's a setting I typically change right away, so I don't even remember.
> On which systems are they hidden?
On most systems. There is a long-standing convention in the Unix-derived world that files and directories with names which start with a dot (this also includes "." and "..") are hidden in directory listings. The main exception is Windows, which inherited its conventions from MS-DOS; the convention there is that files and directories with the "hidden" and/or "system" attributes set are hidden from directory listings by default.
Re: The creeping scourge of tooling config files in project root directories
#64Earlier quoted context omitted.
On which systems are they hidden? I hadn't even considered this issue because no file browser I've used in the last ~10 years has hidden dotfiles. Maybe Windows Explorer does, but that's a setting I typically change right away, so I don't even remember.
`ls` is probably the most important place they're hidden, but the Mac OS Finder honors this convention too.
They are hidden by default to protect newbies.
GitHub users can unhide them.
Re: The creeping scourge of tooling config files in project root directories
#65Earlier quoted context omitted.
`ls` is probably the most important place they're hidden, but the Mac OS Finder honors this convention too.
I think Windows has them hidden by default as well (in explorer).
Since Win7.
But Windows has a lot of problems with hidden files, so a lot of people just set it to not hide any.
Re: The creeping scourge of tooling config files in project root directories
#66Earlier quoted context omitted.
Not "a" requirements.txt file, sadly. I've seen packages with different requirements for building, installing, and testing. All with their own damned txt file. Oh! And don't forget the duplication in setup.py -- you'll want to put your requirements there, too.
As far as I know, Pip doesn't have the notion of dev dependencies, so you need at least two requirements[.dev].txt files.
> As far as I know, Python doesn't have the notion of dev dependencies
Python doesn't have the notion of dependencies.
Pip doesn't have dev dependencies, poetry does.
Re: The creeping scourge of tooling config files in project root directories
#67Earlier quoted context omitted.
Not "a" requirements.txt file, sadly. I've seen packages with different requirements for building, installing, and testing. All with their own damned txt file. Oh! And don't forget the duplication in setup.py -- you'll want to put your requirements there, too.
As far as I know, Pip doesn't have the notion of dev dependencies, so you need at least two requirements[.dev].txt files.
[deleted]
Re: The creeping scourge of tooling config files in project root directories
#68On another note can we talk about the amount of projects that just dump their config/log files in the root directory as a 'hidden' file when you start them? Why? we have a .config for a reason.
[deleted]
Re: The creeping scourge of tooling config files in project root directories
#69Who cares. Get over it.
Just curious, how many icons are on your desktop?
Re: The creeping scourge of tooling config files in project root directories
#70I don't get this, what's the problem here? Having config files in root means you know they can apply to all sub directories. This has nice properties like recursive behaviours (see .gitignore) If you want to put (most of) your config files in a .config folder, then most apps should support that If you want to view your config files in a different way, then actually you're trying to solve a different problem. Perhaps…
A voice of reason