Re:How key-based cache expiration works
by DodgyEggplant on Sunday February 19, 2012 @07:24AM
(#3609199)
It sounds really impressive, smart, innovative UI and underlying architecture. 37 signals did it again!
What is the minimum requirements of a team, programmers/skills/time, to get into such a project and actually deliver?
[ Parent
| on HN ]
Re:How key-based cache expiration works
by DodgyEggplant on Sunday February 19, 2012 @08:26AM
(#3609282)
Why the downvote? It looks like a very promising attitude, but one has to consider if this added complexity is feasible for a smaller or less experienced shop. The input is important.
My guess is that the parent is getting downvoted because it's so dense with hero worship that it turns my stomach.
Re:How key-based cache expiration works
by randomdata on Sunday February 19, 2012 @11:20AM
(#3609615)
Perhaps because the caching methodology in the article has been advocated to Rails developers for several years now?
It was a good refresher for those who have forgotten or are new to Rails (or web development in general), but to call it innovative is going a little far.