|laziness, impatience, and hubris|
Re^2: looking towards learning OOPby spx2 (Deacon)
|on Sep 12, 2008 at 21:49 UTC||Need Help??|
my problem with Moose is that its documentation becomes obsolete
as time passes by and it is spread(presentations,articles,cookbooks,cpan docs) all over the internet.
noone seems to understand that for it to be attractive for developers
it needs to have nicely binded documentation in one place and one place only.
if I go to #moose people are nice, but it is not nice for me to come knocking on
their door each time I hit a bump in the road just because noone took the trouble
to nicely bind and write a good documentation for the project.
and if documentation isn't enough or well written or any at all ,
they suggest to read the source code,but that would be an effort for my side
so big,that it would mean not only I am trying to learn Moose but also it's internals,
the latter of which was not my intention at all.
as a sidenote:
if I want to learn c++ it doesn't require me to understand the internals and/or read it's
source code(altough on some occasions it is useful)I just need to read the description of what each class does,it's methods,some
examples and I can start using it