On Sep 23, 2014 3:17 PM, "sri" <[email protected]> wrote: >> >> Thus I would estimate now + 1 year for an interim solution, if you want to minimize the sum of whining by admins, app-developers and core-developers. > > > I really hope i never gave anyone the impression that one of my goals would be to minimize whining... i will always keep pushing forward, even if those folks have to be dragged along kicking and screaming.
:D That's a really good point. Even seems like that's documented somewhere that Mojolicious is very progressive. While it's awesome the Mojolicious tries to still support CGI, it's just not a progressive strategy and may need to be evicted in order to keep the rest of the project on track with the big picture. That this is, or could be, documented could be useful knowledge to most and exciting in itself for many as a feature and strength of Mojolicious. If someone needs a feature dropped in 5.13 then Mojolicious, for them, is no longer being developed. But there's always Mojolicious 5.44 available and they could update their internal project to be compatible with that version. Likewise the connection goes with the Perl binary itself. Mojolicious tries to extend the life of support for versions by reducing breaking changes and announcing them in advance, but to meet the vision of the project sometimes it will happen that support for your version will end. But why would that matter, since updating the application is clearly off limits why should it matter being stuck on an older version? But I digress as I got off topic, sorry. And, furthermore, I probably once again stand alone with my thoughts. :) -- 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.
