I'm sorry if this isn't really a good question or if the answer is obvious, but why can't things in unix be represented as objects?  For example, files are sort of objects, but they are all just files.  I realize that this can be useful for providing a standard interface, but does it really?  What's the point of something being a file if reading a file doesn't show anything useful like a device file?  I think a device file could easily be an object in a directory, instead of a file.  Then instead of having to run some command like cgdisk, the device object could provide it's own way of changing itself or give information about itself, for example /dev/sda.partition1.get_size().  I think this would be nicer in theory than having a bunch of commands that do different things all in one directory (/usr/bin) and that all have different ways of passing options to them.  If there's something obviously wrong with that idea i'm sorry, but I have a question that has less to do with objects in that case.  Why cant commands be organized in usefully named directories?  For example instead of having every command in /usr/bin, you could have something like /CMDs/devices/list or /CMDs/output/echo hello.  Thanks for taking the time to help a noob out.
Why can't unix be object oriented or at least organized
files;filesystems;unix philosophy