Wouldn't the same be applicable to files, processes, devices and so on?
And like it or not OOP shows that it's possible for one idiom to describe all the things when it's flexible enough.
I've got a lot of experience working in systems that model everything as a series of resources passing messages and it works very well. The entire QNX operating system right down to its POSIX support uses this underlying primitive and, while you would never see it in your own code their system-wide profiler leans on this design to make it easy to see how control flow moves between isolated threads and processes within the software system.
Both "special" and "device" files are still "files".