Making the leap from linear to OO programming is not intuitive nor easy for everyone and the longer you've done the former, the more difficult it is to come up to snuff (as in attaining the same degree of speed/expertise/comfort) with the latter. Learning to write an OO "Hello World" script or similar useless programs doesn't prepare one to convert existing programs or start new ones that make extensive use structures like $employee{ssn}{$PO}{email}.
When I begin the switch (and there is no doubt that I eventually will) it will be done on my own time. I don't have the luxury of doing it on company time since I've got at least a dozen projects already going or on my TODO list and only one or two are with Perl.
My employers don't care if it is OO or not as long as it works. My boss is a bit older than I and although he doesn't do much with Perl, he is an excellent programmer, problem solver and can follow and modify any of the Perl code that I write. He has a similar background to mine and there would be a learning curve for him as well if I switched.
Real world constraints often take precedence over idealized ones. -- jlongino
In reply to Re: Re: Reactions to OO-Perl
by jlongino
in thread Reactions to OO-Perl
by pjf
For: | Use: | ||
& | & | ||
< | < | ||
> | > | ||
[ | [ | ||
] | ] |