On Wed, Feb 4, 2009 at 1:04 PM, Yehuda Katz <[email protected]> wrote: > I guess we can add another special case.
-1. The original poster's complaint seemed like an inconvenience rather than a showstopper, and the suggestion of letting the app live in development but die in production seems totally backwards. In the unusual stated case of "I have a controller that's only invoked once a month, and I was too stupid to run a single test case on it before rolling it to production," the merciful thing to do is let Merb continue to live and let that rare controller action fail, so that every other user of the app can go on with their stuff. Whereas in development, the *efficient* thing to do is kill Merb immediately so that the developer is hit over the head and can't continue until fixing it. At the very least, make it a configuration option and let people decide for themselves in each environment. I suggest calling the option :syntax_darwinism since the question is whether unfit code should continue to live. >8-> Have Fun, - Steve Eley Editor, Escape Pod http://escapepod.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "merb" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/merb?hl=en -~----------~----~----~----~------~----~------~--~---
