use a language that supported objects that could reference other objects, but the references could never be changed to refer to different objects after instantiation? Primitives likes ints and bytes inside of objects could be changed all you wanted. You could have pointers allocated on the stack that point to objects on the heap, and the pointers on the stack could be changed arbitrarily. Insisting that pointers inside of objects always remain constant since instantiation would make it impossible for a cyclic references to occur, so reference counting could be used for general garbage collection in this scenario. So would you use such a language? Or would it be silly, restrictive, and ultimately a waste of your time?
use an IRC network that supported anonymous communication? primitives like LIST, JOIN, PART and PRIVMSG would still work... but there would be no NICK, no KICK and no way to discriminate between users. You could have persistent channels, which save the first (or last) N messages sent to the channel and replay them to anyone joining. Insisting that all communication be done anonymously (+tripcodes) would make it impossible for namefaggotry and egotripping to occur, so tripcode filtering could be used for general shitpost filtering in this scenario. So would you use such a network? Or would it be silly, restrictive, and ultimately a waste of your time?