On 12 Sep 2007, at 22:49, Sandofsky wrote: > It isn't important enough to most users that they'll be forced to do > that.
By the same token they wouldn't be forced to learn a new config setting either, so this consideration is irrelevant in this case. > More functionality means more to maintain, more tests to break, and > more considerations when writing a plugin. In that case should I submit a patch to move RESTful routing into a plugin - after all that's complex area for newbies and there's load of stuff to maintain (only joking). The point I'm trying to make is that deciding on whether to add a feature should be balance between maintainability and usefulness - I personally think the usefulness exceeds the likely maintenance overhead. > HTML4 is fine. But it isn't fine enough that it deserves the support > of Rails. To me that would make Rails dogmatic rather than just opinionated software. If I can generate images with Rails why would should it only allow me to product invalid HTML (as that's what XHTML served as text/html is). Andrew White --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" 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/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
