[dancer-users] Using Dancer2 as a website framework

[John Ingram]

I initially felt the same way when I read that, because I'm a Perl guy, and
I see Perl as being suitable for pretty much anything you want to do.   I
assume that in considering "suitability," Greg is considering things like
"how many of us are comfortable building and maintaining a website in a
certain language."

The truth is that there's nothing unsuitable about any of the languages he
mentioned for the task.  What he's really doing is using Perl for the part
of the project that he wants to use Perl for, and Python for the part that
he wants to use Python for.

Fortunately, Dancer is a really nice way to abstract away stuff that is
most easily done in Perl, so it can be consumed by other languages doing
other things.  Although I would certainly tell him that you can build the
whole thing in Perl -- because you certainly can, I was also going to tell
him that making a Dancer web service would be perfectly good solution as
well.


On Mon, Sep 2, 2013 at 6:41 PM, gvim <gvimrc at gmail.com> wrote:

> On 23/08/2013 11:21, Greg Kempe wrote:
>
>  We're exploring two options:
>>
>>    1. use Dancer to build the entire website
>>    2. use Dancer to power a thin REST API around the library and use
>> another
>> framework (eg. in Python) to build the rich website experience.
>>
>
> I don't quite understand how Python or Ruby is any better suited to
> creating a "rich website experience" than Perl. Front end is HTML, CSS and
> Javascript if you're using a REST API so using more than one server-side
> languaged doesn't make much sense to me.
>
> gvim
>
> ______________________________**_________________
> dancer-users mailing list
> dancer-users at dancer.pm
> http://lists.preshweb.co.uk/**mailman/listinfo/dancer-users<http://lists.preshweb.co.uk/mailman/listinfo/dancer-users>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.preshweb.co.uk/pipermail/dancer-users/attachments/20130902/bdc6f6b4/attachment.htm>