ULib's design requirements

[Megiddo]

I made up a crappy list of design requirements for ULib. Might as well post it in case it can spark some conversation. 

Goals:
· Easy to use authentication system (I have to admit, what we were using is about as easy as possible though)
· Simplify often-used features. IE, vgui.
· Provide a framework for developers to build off of.

Requirements:
· Access system must be able to assign users access on a per-command basis
· Keep out anything that's too specialize (would be served better separate from ULib)

Notes:
· Since GM10 offers a lot of what ULib in GM9 did, perhaps we should take the minimalist approach with ULib in GM10 and offer little other than the access control? Might make it more popular for other developers since they don't seem interested in anything else anyways.

Modules

Basically, the idea behind this is similar to our UGate idea (http://forums.facepunchstudios.com/showthread.php?t=140768). It would allow dynamic loading and unloading of scripts.

Pros:
· Can load and unload on the fly!
· Offers a clean separation between "modules"
· Might be able to implement a help system for each module

Cons:
· Would anyone really use such a feature?
· Hard to get all the hooks used by a script to unhook, etc.