in reply to Re^2: Perl AJAX jQuery, js file
in thread Perl AJAX jQuery, js file

I certainly hope that spending my time to extract the logic from your Mojo code, won't force me to include Mojolicious in my CMS.

No, definitely not. Mojolicious does have its advantages though ;-P

Replies are listed 'Best First'.
Re^4: Perl AJAX jQuery, js file
by monx663 (Sexton) on Jan 11, 2021 at 13:21 UTC
    I know Mojo is great stuff and I read its docs before, but it's too full of functionality! :( I prefer to have code that looks like racing cars look on the inside. No door handles. Jump out the window, when you park! :p
[reply]

      "...but it's too full of functionality! "

      The advantages of using a framework like Mojo is that you get all the benefits they bring, but nobody forces you to use each and every feature. Your application code is separate from the base framework, so caring about things which won't impact you (should you choose not to use them) seems illogical. Writing a safe CGI and DBI "from scratch" seems fraught with risk for little reward compared to something like Mojo/CGI & DBI, which all have literal years of developer time spent honing the solutions.

[reply]
        I was writing Perl when every Mb of RAM saved and milliseconds of code interpretation, counted, in complex and huge data structure processing.
        I got the "count your pennies" coding mentality from those days :p
[reply]

        You know, I think you were right about Mojo. I bit the bullet and will use it, seeing it seems to be able to help rid my project of other CPAN dependencies and seems light enough for all it does.
        It looks great stuff and I've just begun reading up on it in order to incorporate it with Bootstrap and jQuery, into the 21st century version of the CMS.

        Wish me luck!

[reply]

In Section Seekers of Perl Wisdom