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

Looks promising...
Thanks, dude!
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.
Because the CMS is streamlined like a speeding cheetah. Even its CGI.pm and DBI.pm are written from scratch. We don't want no f^&%ing bloated code in these here, mod_perl parts! :D
Cheers!

Replies are listed 'Best First'.
Re^3: Perl AJAX jQuery, js file
by haukex (Archbishop) on Jan 11, 2021 at 13:00 UTC
    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

      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

        "...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.