Practicing PrototypicalPrototypal Code
I'm focusing on practicing a very prototypicalprototypal structure with my code (non library oriented) to begin learning to reuse large portions of my application infrastructures where applicable in future projects. With this in mind, I don't have experience with prototypicalprototypal programming before now, and would like to ensure that I'm not misusing the strategy.
The following server side JavaScript code has the purpose of handling a large number of Socket.io events in a modulated, prototypicalprototypal way. My goal is code that is readable, but also reusable. I feel as if I may be sacrificing the clarity of my code in order to utilize a prototype for the handlers; it eliminates the inclusion of duplicate code in each handler, most of which helps with debug logging, but it may make the code less readable. I'm interested in learning whether or not this is an unavoidable aspect of using prototypes, or if there are ways that I may use prototypes without diminishing readability.
Most importantly, I'm interested in feedback on the comparison between the prototypicalprototypal and non prototypical-prototypal event handling, and whether or not I'm using that strategy correctly.
