comment on

You can't always interpret a lack of buzzing around as stagnation. The Template Toolkit hasn't had much new core development for years: that's because it's complete. Dancer2 core is not as complete as TT, but it's very full-featured and stable, and the plugin architecture means you can easily build your own if something's missing. Most of the things introduced to core started as plugins anyway.

As far as what I use Dancer and Dancer2 for : all the new webapps and APIs I build, which is most of my work: "microservices" where the bulk of the requests are for REST endpoints rather than traditional HTML page content. I also have plenty of more human-oriented websites on Dancer/2. (I just started a $job where the app framework is Mojolicious, though.)

The way forward always starts with a minimal test.

In reply to Re^3: Dancer2 developers on PerlMonks? by 1nickt
in thread Dancer2 developers on PerlMonks? by nysus

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Clear questions and runnable code get the best and fastest answer
	PerlMonks