The development of Catalyst was moving fast and I think this was a good trade off for documentation and API stabillity at this stage of development. I know you can use this reasoning as an excuse for every project and I don't have any ready theory here - but for sure it depends on the size of the project and Catalyst being quit a big one needs some more time in the 'rapid prototyping' phase.
Now the documentation is improving and I believe the API is quite backward compatible.
in reply to Re^3: Perl is dying
in thread Perl is dying