What is wrong with using a structure that has many dependencies?

Question

I recently told a friend that I was starting to learn Catalyst (Perl), and he emphasized quite a lot that since Catalyst involves so many dependencies, I should use something like Rails instead.

Isn’t it good that there are many dependencies? Doesn't that mean a lot of code reuse? I understand that there can be more effort when installing the framework, but are there any other disadvantages?

I will return to the tutorial until I get a few juicy answers. :-)

Answer 1

, (, ) , .

, . , , , .

, .

. Ruby , , , .

, ​​ "", .

Answer 2

. Catalyst , , Catalyst. , , .

, , , CPAN Catalyst. , . Debian apt-get install libcatalyst-perl 15 - Perl. 15 . ( CPAN , , CPAN , .)

, , .

Answer 3

, . , , .

:

. . . " , , ?"

: " , ?"

: " , , , , -?"

Answer 4

, , , . , (- , , ) . , gcc 4.0.3 foo, ( foo), gcc 4.0.5 , foo. , 4.0.2 .

, , , "Frankenstein monsters", , , . . , , .