Ted proposed it and I liked it, though I admit that these first 2 profiles aren't particularly useful, but they put recommendations for what constitute good long and short cache times into code (rather than just into documentation). Also, by naming them/having a reference to them, it gives us the freedom to change the value wherever it occurs (either by overriding it or changing it at the library level).

On the topic of these profiles, think of them like mixins for the options object, where you can set your options more abstractly (if you like), rather than setting a specific number, e.g. `options = Utils.extend({}, profiles.LONG_CACHE, profiles.HIGH_QUALITY, profiles.BIG)