Slashdot Mirror
Shuttleworth On Redefining File Systems
moteyalpha writes "Mark Shuttleworth described the beginnings of what could a great step forward in making file systems more usable. I've personally had the experience of trying to find a file for a customer who had just finished editing a critical report, saved it, and then couldn't locate it to deliver to their client. Quoting: 'My biggest concern on this front is that it be done in a way that every desktop environment can embrace. We need a consistent experience across GNOME, KDE, OpenOffice and Firefox so that content can flow from app to app in a seamless fashion and the user's expectations can be met no matter which app or environment they happen to use. If someone sends a file to me over Empathy, and I want to open it in Amarok, then I shouldn't have to work with two completely different mental models of content storage.'"
Is a new file system really necessary for doing that? How about just restricting the user to what directories he's saving files to. ie:
.imafuckingstupididiotwhoiswastingyouroxygen go to the imafuckingstupididiotwhoiswastingyouroxygen folder
.doc files go to the "doc" folder
.txt files go to the "txt" folder
.jpg files go to the "jpg" folder
Think of it as a car problem. The user is having a hard time remembering how to keep the car on the road. Instead of redesigning how the road is constructed, install guard rails. If the driver still manages to drive the car off the road, the driver is an idiot and the gene pool is better off chlorinated.
greed@All_Evils:~#
Love your sig. Been telling the Twitter-hunters for a while now they're wasting their time.
Linux, you magnificent bastard, I read the fucking manual!