Greetings, I am using Mojolicious for two large enterprise applications and this feature is of potential benefit. In a complex enterprise application with thousands of elements the matriculation from desktop to mobile often involves far more than simply swapping css or javascript behaviors.
Personally I don't think this framework should be encouraging or discouraging much of anything. If I wanted built in shackles I could just use rails. One of the great strengths of Mojolicious is it flexibility and essential perlish philosophy. While we have a crude solution internally to deal with this issue already, it would be preferable for us to have access to a cleaner baked-in version from the framework. As Ben pointed out, no one is forced to use it and it defaults gracefully to the current paradigm. TIMTOWDI. If templates are well structured this feature can be used more as an aggregator of template fragments rather than swapping one template for another with all the implied duplication. This is my first post and I would be remiss if I failed to express my gratitude to Sebastian and the rest of the team for the awesomeness that is Mojolicious. Mojolicious has allowed me to deploy complex applications more quickly, more enjoyably and with less labor than any other framework I have encountered. Simply put, I find it brilliant from toe-tip to crown. Sincerely, --Will -- You received this message because you are subscribed to the Google Groups "Mojolicious" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/mojolicious. For more options, visit https://groups.google.com/d/optout.
