Yeesh. If you can say with absolute certainty that you'll never need the command line with your MP3s, I suppose you could go with a hideous monstrosity like that. Personally, I usually don't care about anything except the title and occasionally the artist, so those are what I put as the filename. Filenames still tend to be long, but they aren't impossibly long.
I think you are also confused about what people mean when they are saying "metadata" in this context. The more common term for it is probably "extended attributes." It provides a trivial mechanism for storing key/value pairs associated with an inode. There's no reason you couldn't have a "Composer" key, or any other kind you wanted.
A truly intelligent file browser could be configured to display metadata selectively, sort on it, and so on. That may become a reality in Linux as a metadata-capable API emerges.
I tend to agree that metadata-in-files is a messy approach. It is better to have a distinct source for it, and filesystem-based metadata might be the solution. I guess we'll have to wait and see if it really is.
This doesn't really involve any exercise, but find a big parking lot that's empty on weekends and buy a bunch of traffic cones. Set up a course with the cones and do timed runs. Or if you have a truck, find an off-road course somewhere (do not just go anywhere!) and run that. There are clubs everywhere if you want to do those with other people. Most car clubs will also rent local racetracks and have "driver's ed" classes for a hundred bucks or so. Some car clubs - the BMWCCA, for example - will also get you discounts on parts at car dealers or on the purchase of a new car (really).
Not really exercise, but it gets you out in the sun. And if your heart isn't racing by the end of your run, you're not doing it fast enough or hard enough.
Speed doesn't often cause accidents. Poor driving causes accidents. This is a common misconception sponsored by the government (and I have no idea why they keep spreading it).
A car driving 90 in the passing lane isn't going to cause an accident unless he rams someone. Odds are, if he rams someone it's because a person pulled right out in front of him. Odds are, that person didn't check his rear-view mirror before changing lanes.
The one time when speed can "cause" an accident is when a driver loses control of his car. Which is still not really caused by the speed, it's caused by the driver of the car not knowing how to drive. That is, if the driver knew how to handle high car at high speeds, he probably could've avoided an accident.
Most of our automotive laws are actually built around this. If you cut someone off in traffic and get rear-ended, you're legally at fault: no matter how fast the other car was going, you are responsible for judging how much room you'd need to move in. The way our laws are written that way is to accomodate the common scenario where traffic is stopped in one lane on the highway, but continues at 30-40mph in the next. It applies just as well to when traffic is moving at 60mph in one lane and 90mph in the next.
The primary effect speed has on accidents is that it makes them worse. It also exaggerates mistakes made by bad drivers and makes dangerous cars more dangerous.
I have to agree with the semi-original poster here. Some drivers are safer at 80mph than others are at 60mph. Unfortunately, insurance companies can't charge based on driving ability, because the bad drivers would end up shouldering the entire cost (which would include things like hospital stays) and good drivers would pay almost nothing. I'd support that, myself, since I'd end up saving about $1000 a year.
Slashdot Mirror
I think you are also confused about what people mean when they are saying "metadata" in this context. The more common term for it is probably "extended attributes." It provides a trivial mechanism for storing key/value pairs associated with an inode. There's no reason you couldn't have a "Composer" key, or any other kind you wanted.
A truly intelligent file browser could be configured to display metadata selectively, sort on it, and so on. That may become a reality in Linux as a metadata-capable API emerges.
I tend to agree that metadata-in-files is a messy approach. It is better to have a distinct source for it, and filesystem-based metadata might be the solution. I guess we'll have to wait and see if it really is.
Not really exercise, but it gets you out in the sun. And if your heart isn't racing by the end of your run, you're not doing it fast enough or hard enough.
A car driving 90 in the passing lane isn't going to cause an accident unless he rams someone. Odds are, if he rams someone it's because a person pulled right out in front of him. Odds are, that person didn't check his rear-view mirror before changing lanes.
The one time when speed can "cause" an accident is when a driver loses control of his car. Which is still not really caused by the speed, it's caused by the driver of the car not knowing how to drive. That is, if the driver knew how to handle high car at high speeds, he probably could've avoided an accident.
Most of our automotive laws are actually built around this. If you cut someone off in traffic and get rear-ended, you're legally at fault: no matter how fast the other car was going, you are responsible for judging how much room you'd need to move in. The way our laws are written that way is to accomodate the common scenario where traffic is stopped in one lane on the highway, but continues at 30-40mph in the next. It applies just as well to when traffic is moving at 60mph in one lane and 90mph in the next.
The primary effect speed has on accidents is that it makes them worse. It also exaggerates mistakes made by bad drivers and makes dangerous cars more dangerous.
I have to agree with the semi-original poster here. Some drivers are safer at 80mph than others are at 60mph. Unfortunately, insurance companies can't charge based on driving ability, because the bad drivers would end up shouldering the entire cost (which would include things like hospital stays) and good drivers would pay almost nothing. I'd support that, myself, since I'd end up saving about $1000 a year.