/prog/rider's secret society

We should create a club/lodge for programmers. If stonemasons created one many years ago just because they knew how to carve stupid stones and build some basic structures, why we still don't have one?
This is what we need:
◦ A symbol.
◦ A secret handshake.
◦ A set of rules.
◦ An unknown leader.
◦ An unknown sub-leader.
◦ A library with exceptional computer books, a printed version of world4ch's /prog/ (aka The Old Testament), ancient computers, and other relics.
◦ A list of heretic languages carved in stone.

>>50
The difference between objects and files is that the interface to a file is a stream of characters, and the interface to an object is a dictionary (i.e. set of procedures) over that object. A file can be an image, or a geometric description, or a document and your interface to that file is still getchar, and not something more appropriate. You can later paper over it in some way, but that's the fundamental interface a file system provides. Compare this to the hypothetical transparently persistent object store you mentioned (which would be the equivalent of a file system).

Some operating systems (e.g. Amiga OS and BeOS) papered over files very well with ``datatypes'' as part of the services the OS. This is one step up from the usual UNIX nonsense, but it sits on top of a layer that was the wrong abstraction in the first place (files), so this is not very good (hence why I said ``papering over'').