in reply to Re^10: How do I go from procedural to object oriented programming?
in thread How do I go from procedural to object oriented programming?
That is not a suggestion. That is an accusation. The context behind "Just say no" is illicit drugs.
If you assess the code at hand, you would see that Moose will not hamper execution time like you would have people believe. Why? Because the only dynamic element of the code at hand is to stitch together rendered pieces of HTML. The generation does not need to be performed when the content is requested, only when content is updated. And you know this to be true.
We have already pointed out that even if you accusation were true, the problem is easily solved by either using another means to create objects or by using another means to handle CGI. And yet you insist this not to be true.
As for your artificially concocted "constraint" ... that is not a real world problem. Real world problems arise because of things that you truly cannot change right now -- hosted websites can change, if their authors change. Company X not being able to change providers due to contracts, that is a real world problem. And you know this to be true.
But you'll reply and deny all of this anyway. So go ahead ... in the end, what has changed? Not a damn thing other than a node inc. And you know this to be true.
In the mean time, the rest of us will continue to use Modern Perl and be successful. You only wish that were not true.
|
---|
Replies are listed 'Best First'. | |
---|---|
Re^102: How do I go from proc to OO? (not how do i confuse and spread FUD)
by Anonymous Monk on Apr 23, 2015 at 02:56 UTC | |
by Anonymous Monk on Apr 23, 2015 at 03:26 UTC | |
by Anonymous Monk on Apr 23, 2015 at 03:30 UTC |