View Single Post
Posts: 992 | Thanked: 995 times | Joined on Dec 2009 @ California
#100
Originally Posted by TiagoTiago View Post
What is the point of having thigns actually be just files in the filesystem if it's just a mess of things piled up in the same place? If there is a whole layer of software making that mess not be a mess, then whats the point of using the file system ?
It is easy to do a mess with registry too. Registry just creates some order but this order has it's own problems.


The point is having things be organized, if there is need to always know where somthing is, don't hardcode a path, use a way that no matter where the things is, you know it (like an environment variable, or identifying the path for the thing somewhere, be it a registry, or a filesystem abstraction like symlinks that always have the same name, under a folder that is always the same etc). Hardcoding values that people might have some reason (even reasons you can't think off) to want to change, is a bad habit.
Good point about order.

However, the hardcoded path problem does exist only in N900. The messy file location may be a problem too but I suspect you just don't know yet the reason why this file is put in that place.

And again - messy environment is easy to do with registry too. It is just M$ who maintain some order in Windows registry, without them it could be a bigger mess (I just remember the early days of Windows).