in reply to Any gotchas with CGI and Mouse running together?

When you created hand-craft classes did you create get/set methods for all of the object attributes? This is one of the cons of Moo(se), you are forced to trade encapsulation for convenience.
  • Comment on Re: Any gotchas with CGI and Mouse running together?

Replies are listed 'Best First'.
Re^2: Any gotchas with CGI and Mouse running together?
by kcott (Archbishop) on Feb 26, 2015 at 01:55 UTC

    Thanks for the reply. I really was just after any issues that may have been encountered with the CGI+Mouse combination.

    -- Ken

[reply]
      I've used Mouse and Moo under CGI in the past, and found response times with Mouse noticeably longer. However I wouldn't use Moo for new projects because of the anti-modular code that results from it.

      I hope you wouldn't mind if I rephrase the question you didn't answer. Which of the following statements is correct?

      1. You don't realise how anti-modular Moo is
      2. You know that Moo is anti-modular but don't see that as a problem
[reply]
        Please, can you elaborate on 1.? Or at least provide links to already existing nodes/blog posts related to the issue?
        لսႽ† ᥲᥒ⚪⟊Ⴙᘓᖇ Ꮅᘓᖇ⎱ Ⴙᥲ𝇋ƙᘓᖇ
[reply]

        Re response time. Unless you did not have XS Mouse installed this is impossible. Mouse with XS will beat Moo in all equivalent use cases.

[reply]

        Thanks for the follow-up and no problem with rephrasing the question.

        Up until you posted this, I hadn't seen any discussion regarding Moo being anti-modular.

        I don't know if the concern here is that Moo readily implements a poor modular design, or that Moo generates poor code from a good design.

        I've designed my interfaces and started to code the framework in Moo. I see no lack of modularity at all at this stage. I'd be interested in any heads-up regarding problems that (perhaps you think) will present themselves later on.

        -- Ken

[reply]

In Section Seekers of Perl Wisdom