No offense, but this is kind of retarded. Code takes up space. Whether it's in the form of a pre-written, tested and robust module or in the form of proprietary code that you write/re-invent specifically for this project, it's going to take up disk space. I'll leave it up to you and your admins to determine which solution takes less time to code and support.
Granted, in this case you can get by with a small amount of code, I think it's rather silly to deny the installation of modules because of disk space restrictions. Perl code doesn't take up a lot of space anyway, and disk space is cheap.
| [reply] |
I totally agree with you, code does take up space, why not allow the installation of modules if it helps make the code shorter, that's an awesome argument. However, his retort will be, "Your lucky I'm letting you do this". It all started out with me maintaining, and updating the current applications that he built in C. I decided C was functional, but that there had to be something better out there. So I was poking around, and saw how much of a fan base perl has and decided I'd try it out. When I made him aware of my plans he was weary. However he is letting me experiment with it to see what I can do. Now that I've written a prog that would have taken probably 1,000 lines of code in C(if it was at all possible to build something like that in C to begin with) he will more than likely be more lenient.
True?
| [reply] |
Show him a Perl script that'll do the job you need in 10 lines of code (assuming a few additional modules get installed) and he'll be impressed even more.
| [reply] |
