> Let's wait five years and see if there is actually any consensus on it being needed and used at all, rather than rush into something just because "we can".
This is why every project maintainer dreams of being Linus...
This is why every project maintainer dreams of being Linus...
Also very useful for photographs for example, when you can edit the EXIF without the whole lot becoming randomly sorted.
Because updating atime on every file access carries an IO overhead, there's a mount option "relatime" that only updates atime if atime < mtime. This preserves the "new mail" feature of mutt, but doesn't require atime writes for every file read operation, which is a decent compromise.
Most people who try do it poorly though. You have to be super smart to reject unneeded stuff while still allowing useful features to go through.
I'm not sure "it's" really about taking responsibility for all the consequences of your decisions seriously, as much as it is creating the space and mechanisms for your ideas to come to fruition. We cannot "see" the consequences of our actions, but we can create systems that stabilize the world. Perhaps this is what you're talking about?