"...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] [Watch: Dir/Any] |
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] [Watch: Dir/Any] |
"Back in the day", hardware was EXPENSIVE, not to mention the cost of the physical space, power and cooling that it required. This was where managers "counted pennies". The programming style that you describe was needed to make things work in the environment that we were given. Today, the cost of programming, especially maintenance, far exceeds the cost of hardware. Tools that reduce these costs are almost certain to reduce the cost of a project. It simply does not mater that they 'waste' hardware resources. Old habits die hard, but pennies still count.
| [reply] [Watch: Dir/Any] |
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] [Watch: Dir/Any] |
Please start a new thread with any related questions you may have. Mojo just makes life as a developer easy and fun again. Sort of related, for personal work I ditched jQuery, bloated. Consider You might not need jQuery.
| [reply] [Watch: Dir/Any] |