Re^5: Disputation of g0n on the power and efficacy of XS

I'm not missing the point: I just don't agree with yours. There's a difference.

You have to install software on a bunch of different architectures, machines you don't have access to, and you have to fight a bureaucracy. I don't see how any of those problems are solved by anything we're talking about. You still have to install software on a bunch of different machines of different architectures and you still have to deal with the bureaucracy.

I've been in that situation, and I always had CDs with all the binaries I needed. I compiled everything I needed and then I had it. Installing it on one machine or a hundred made no difference to me. Finding popular libraries is very easy, finding binaries of them is very easy, and in most cases compiling them is five minutes of work to get the thing going. After that, it doesn't matter if it's Perl or C or Java or anything else: you still have to push it to all the machines.

I wouldn't keep around a sysadmin who couldn't do this easily, and I certainly wouldn't tolerate any whining about it being too much work when I know it's not. This is not the sort of problem that a good sysadmin seriously complains about.

So, you have a tough job, and you know Perl. Let's see some code that solves it. Perl's all about making the hard things possible, so the people who keep complaining about hard things just aren't trying.

--
brian d foy <brian@stonehenge.com>

Comment on Re^5: Disputation of g0n on the power and efficacy of XS

Replies are listed 'Best First'.
Re^6: Disputation of g0n on the power and efficacy of XS by Tanktalus (Canon) on Apr 21, 2005 at 14:04 UTC
You mean, I should write code to do an Automated module install? Part one was "easy" (only took me about 10 hours so far to code and test on Linux, AIX, Windows). Part two, the part I was referring to above, is something I'm not even really sure where to start. Determining what the external dependancy is, programmatically, is not something I'm looking forward to. Figuring out dynamically that XML::Parser requires expat (and then automatically finding it), while figuring out that Crypt::SSL requires OpenSLL (and then automatically finding it), and any other module I may need to distribute ... that's not going to be fun. More likely is that I figure out my own dependancies by hand, then manually acquire the source/binaries, and then write code that handles that instead. It's not hard, it's just work. Note that dynamically figuring out that XML::Twig required XML::Parser was painful enough - I'm not sure I want to go through it again for the external libraries ;-) This was due to Makefile.PL-based modules and Build.PL-based modules wanting to do everything differently. And I didn't really want to start parsing perl - perl itself has a hard enough time doing that, and I'm not nearly smart enough to write code to do it. So I kick off the .PL script and parse the output (which is why I had to work out why opening '-\|' on Windows wasn't working). I'm not linking to my old articles for people to vote on them. I'm linking to them to show that I'm already trotting down the proffered road and encountering issues which I really hoped I wouldn't.	[reply]

Replies are listed 'Best First'.

Re^6: Disputation of g0n on the power and efficacy of XS
by Tanktalus (Canon) on Apr 21, 2005 at 14:04 UTC

You mean, I should write code to do an Automated module install? Part one was "easy" (only took me about 10 hours so far to code and test on Linux, AIX, Windows). Part two, the part I was referring to above, is something I'm not even really sure where to start. Determining what the external dependancy is, programmatically, is not something I'm looking forward to. Figuring out dynamically that XML::Parser requires expat (and then automatically finding it), while figuring out that Crypt::SSL requires OpenSLL (and then automatically finding it), and any other module I may need to distribute ... that's not going to be fun.

More likely is that I figure out my own dependancies by hand, then manually acquire the source/binaries, and then write code that handles that instead. It's not hard, it's just work.

Note that dynamically figuring out that XML::Twig required XML::Parser was painful enough - I'm not sure I want to go through it again for the external libraries ;-) This was due to Makefile.PL-based modules and Build.PL-based modules wanting to do everything differently. And I didn't really want to start parsing perl - perl itself has a hard enough time doing that, and I'm not nearly smart enough to write code to do it. So I kick off the .PL script and parse the output (which is why I had to work out why opening '-|' on Windows wasn't working).

I'm not linking to my old articles for people to vote on them. I'm linking to them to show that I'm already trotting down the proffered road and encountering issues which I really hoped I wouldn't.

[reply]