<div dir="ltr">Use other language for the frontend may have some advantage. The first I see, is that you can have more developer available in other language to maintain the frontend.<div><br></div><div>It's easier to find PHP Zend developer than Perl Web developer. Also true for python.</div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">2013/9/3 gvim <span dir="ltr"><<a href="mailto:gvimrc@gmail.com" target="_blank">gvimrc@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On 23/08/2013 11:21, Greg Kempe wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
We're exploring two options:<br>
<br>
1. use Dancer to build the entire website<br>
2. use Dancer to power a thin REST API around the library and use another<br>
framework (eg. in Python) to build the rich website experience.<br>
</blockquote>
<br></div>
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.<span class="HOEnZb"><font color="#888888"><br>
<br>
gvim<br>
______________________________<u></u>_________________<br>
dancer-users mailing list<br>
<a href="mailto:dancer-users@dancer.pm" target="_blank">dancer-users@dancer.pm</a><br>
<a href="http://lists.preshweb.co.uk/mailman/listinfo/dancer-users" target="_blank">http://lists.preshweb.co.uk/<u></u>mailman/listinfo/dancer-users</a><br>
</font></span></blockquote></div><br></div>