Re: UP-TO-DATE Comparison of CGI Alternatives

[ajmetz82]

Did anyone go ahead and start such a FAQ?

I just discovered this conversation thread via google, and it seemed a great idea!

Did anyone make a start on collecting opinions, or people's likes and dislikes of each, as suggested in this thread?

I learnt Mojolicious in 2015, and Catalyst in 2016. Most of the sites I work on, were started in 2016 on Catalyst, only I'm contemplating whether I should do a few projects in Mojolicious again too, so I can keep up my familiarity with both frameworks, or whether it really is easiest to just stick to using one, ^_^. This led to me googling Catalyst or Mojolicious for which this thread (once limiting search results to the past year) was the top result.

[1nickt]

See this node in the thread.

[ajmetz82]

The point on the usefulness of a deployment guide in that linked to node, is also heard.

[ajmetz82]

Thanks! =D

That post points out a minimal and simplistic guide would be easiest to maintain.

Do we know though, if anyone who expressed interest in this idea on this thread, has begun such a guide yet or not?

[Perl300]

I found this node the same way and am thankful that this question was asked and discussed. I have not tried any framework yet and was trying to find which would be the easiest to learn and I think I got my answer.

It's Mojolicious!

[Your Mother]

You might be right that it's the easiest but it does have a bit more off-center DWIW magic than the others. What I think it does do best is its helper (like Mojo::DOM) and testing utilities. Please avail yourself of the testing especially. I don't think anything else makes it easier to write tests against web applications; Selenium being an exception perhaps because you can record tests and they respect JavaScript too.

Update: added <abbr/>.

[Perl300]

Thank you Your Mother for the additional inputs. I had to google for DWIW but know what it means now :-)