On Wednesday, August 27, 2014 9:03:21 PM UTC-6, sri wrote: > The feature proposal in this branch may seem rather simple, but it > represents a possible new chapter for Mojolicious. > > https://github.com/kraih/mojo/compare/time_in_words > > We are not at the point where we are going to select a "blessed" model > layer. But what we could do is shift away a bit from trying to provide only > the absolute essentials, and start embracing more (and higher level) > established best practices from outside the current Perl eco system, such > as cutesy dates. What do you think, where should we draw the line when it > comes to high level features? >
I don't know if there is such a line as long as there is a compelling need. A rule of thumb I (try to) follow with my own software is "would this delight people?" If Mojolicious had a tagline, it would be "Look how simple it is to do amazing things!" I think any feature that supports that is worth consideration. With the cutesy dates specifically, however, we would probably want to make it I18N-able, which could open up a worm can, since (I think...) this would represent the first Mojo::* whose content isn't configurable (e.g. with a template). Is that right? Besides that small issue, I don't have a personal need for this kind of thing (I usually reach for Time::Piece these days), but others may have a stronger opinion. -- 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.
