> My impression is that the language which is making the most > inroads on traditional Perl areas is PHP. Is that because of the > wonderful certifications that PHP has which Perl doesn't? Or is > it because PHP is seen as easier to get started with than Perl? > Also PHP has the huge advantage that hosting environments > allow it to be used in a shared hosting environment, while > mod_perl requires dedicated servers. (That is because PHP is > less capable, so it is hard for one site to cause problems for > other sites running in the same Apache process.)
Are you telling me that this DOESN'T keep you up at nights? I know I'm exaggerating, but this is partly what gets me riled up: that simply because something is easier to get started with it's better. Hell the PHP documentation itself explains why it's easier to get started with: it gives su-root permissions on install. So you don't need to configure anything. Just sit down and play; no worries about not being able to do anything, because you basically have root. I'm sorry, but I'm not willing to take on that huge a security hole just to make the setup process easier. To me this just gives me more reason to fight harder to tell managers that Perl is the way to go. > Suppose that we try this and it doesn't work. Does the argument > then become that we need to get our certification backed by > someone prominent because a certification that nobody has > heard of is proving to be useless? We're just trying to find ways to communicate to managers that know nothing about Perl. This is just one idea. And I think well worht TRYING. > Also I have a different theory. My theory is that the non-savvy > manager is going to ask someone he trusts for an opinion, who > is either going to be someone whose competence has been > proven (less likely), or is going to be someone else of about > the same position and abilities (more likely). In neither case > does the existence of a certification enter into the process. Well if he is "about the same position and abilities" then the certification program will be advertising to him/her as well. > So now I need to take an endless stream of training from an > approved source? Well, as was explained before. Certification is only PART of the hiring process. If you get one certificate and then spend years working with perl you obviously don't need another certificate. Your experience will trump your certificate at that point. > And remember to give the "correct" answer > on a test even when I think it is wrong? (Quick: is "our" a good > thing? Read http://www.perlmonks.org/?node_id=48379 > before answering. Yet as cool feature of the day I'm sure that a > certification would have required me to talk up how great it was.) Well, chalk that up to the proper design of the certification program. At this point we're past deciding whether or not to DO the certification. We're at the point of deciding how best to do the certification. > A certification that has very prominent and vocal opponents > within the community is likely to have an uphill battle to > acceptance. A certification that didn't have enough support > for people to learn what they need to pass it is going to find > that the hill is looking more like a cliff. I thought we were discussing this because we were already looking up said hill. And my understanding of a certification program includes the educational system required for people to pass the exam. Like most Java certification programs these days: you go for 5 days of training and then take an exam. Again, at this point we are talking about the design of the certification, not whether or not to HAVE one. Plus, there'll ALWAYS be ney-sayers. That doesn't really need to MEAN anything other that proof of our diversity. > Trust me, when people go and complain about Perl's > shortcomings, they're not likely to complain about ther > training (or lack thereof) or certifications. They complain about > everything that they dislike about Perl. The only time that I > see people talking about the importance of lacking a > certification is when they're arguing that Perl needs to have > certifications. You can complain about anything you feel like complaining about. This is part of our nature. People will always find things to complain about. People LOVE knocking UNcool things. Part of the idea of a certification program is to make Perl a little more "In" than it is now. Java is not a perfect language but you don't hear too many people complaining about it. It's too popular. Just think "highschool". > Perl is used for a lot of different things. Perl tends to be good > glue. Which means that you need to understand the things that > you're trying to glue together. > > It will be difficult to impossible to provide a single curriculum that > addresses all of the different needs to be useful everywhere from > mod_perl to database processing to bioinformatics to system .... > No simple certification is going to address this problem. I don't consider this a huge problem. Certification is not meant to teach everything that is needed. It's really just to give enough of a taste so that they know how to run on their own. --Alex _______________________________________________ Boston-pm mailing list Boston-pm@mail.pm.org http://mail.pm.org/mailman/listinfo/boston-pm
