Michael Shields wrote:
>
> In article <[EMAIL PROTECTED]>,
> Derek Glidden <[EMAIL PROTECTED]> wrote:
> > Like at least a couple others who've chimed in on the list, I am not by
> > nature a Perl hacker. Trying to wrap my brain around Perl to implement
> > a custom client for my company has been a chore. Add to the fact that
> > the API is at times inconsistent (domain or reg_domain? just a cookie,
> > or cookie, reg_username and reg_password?) and it's been quite a
> > challenge for me. I much prefer, shall we say, a more strict and
> > structured language like Java or C.
>
> "Structured" languages do not necessary lead to internally consistent
> API or protocol design, and vice versa. Please target the actual
> problem.
What the hell does that mean? The whole point of my comments was to
"target the actual problem" by trying to make a point that a less
Perl-oriented API would be beneficial to a lot of people. If it so
happens that I prefer to write in Java than Perl, because I am more
familiar and comfortable with Java than with Perl, is that a problem?
If so, it seems to me the Tucows fellows should just rename "OpenSRS" to
"OnlyPerlSRS" and be done with it and go ahead and permanently piss off
and drive away anyone who has any hope of convincing them to move to
something that's not Perl-specific. Since they don't seem to be doing
that, I'm assuming you're just a Perl bigot taking any meager
opportunity he can to slam someone who is not a Perl bigot.
EOT
--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
With Microsoft products, failure is not Derek Glidden
an option - it's a standard component. http://3dlinux.org/
Choose your life. Choose your http://www.tbcpc.org/
future. Choose Linux. http://www.illusionary.com/
