use Perl

• Are you planning changes we don't know about? (Score:1)

  by Stevan (6065)

  We have a better object system than you do! Just install Moose (but be aware that it might have backwards-incompatible changes in a few months)

  What changes in a few months? I am not aware of such plans. We are generally highly responsible about our backwards incompat changes. Changes happen and sometimes they are hard and ugly, this is the real world after all and they need to happen. But ...

  I suspect your just being sarcastic and playing the devils advocate here. Your right, having a decent object s
  • Re: (Score:2)

    by Ovid (2709)

    Yes, I am being a bit sarcastic, but more than once we've not been in a position to update Moose on our BBC project because of Class::MOP (and this has happened with Catalyst, too). The most important Perl projects and the ones we depend on are the ones we have difficulties keeping up with. Even if you rarely change Moose, or Class::MOP, or Catalyst, or [insert favorite module here] with backwards-incompatible changes, then you have to consider the chance of said changes happening in all of them, not just
    • Re:Are you planning changes we don't know about? (Score:1)

      by Stevan (6065) <reversethis-{moc ... {elttil.navets}> on 2009.12.01 12:44 (#71287) Journal

      Yeah I know, I still have servers running Moose 0.24, so I am with you. We have been discussing trying to make these things smoother in various ways so that people can upgrade and say, get a performance improvement, but opt out of a feature/API change. Similar to the use feature in 5.10. It is still not perfect, but it might help ease those of us (me included) who have to deal with production environments all the time and for whom upgrading it usually not an option.

      Reply to This

      Parent