4 ms·
Extremely poor design: * Not DRY. What if I want to use a cache for production but disable caching in development? And I have 10s or even 100s of functions tha
by coleifer 7y ago
Extremely poor design:
* Not DRY. What if I want to use a cache for production but disable caching in development? And I have 10s or even 100s of functions that rely on the cache? Because the decorators contain implementation/client-specific parameters, I now have to add another entire layer of abstraction over this.
* Implementation is tied to the decorator, e.g. `ring.memcache` -- seriously? Why does it matter?
* What about setting application defaults, such as an encoding scheme, a key prefix/namespace, a default timeout?
I'm sorry but this is over-engineered garbage and good luck to anyone who uses it.
- youknowone 7y agoI agree they are missing features but still they are easy goal with small refactoring so it will be solved soon. Issue #129 is about application default. After that, dryrun is just replacing default action from 'get_or_update' to 'execute'
- whalesalad 7y ago> I'm sorry but this is over-engineered garbage and good luck to anyone who uses it. I agree and wish people would speak up and share sentiment like this more often.