NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
Complexity
More |
Login
| Reply
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
:-)
--Larry Wall in <1991May31.181659.28817@jpl-devvax.jpl.nasa.gov>
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
a bigger rug (Score:1)
/s
Re:a bigger rug (Score:1)
It's an interesting angle, but I think writing the same thing in Perl is rather a more efficient way of managing the same amount of complexity.
But the custom-vs-standard-protocol issue can be an example of implementation complexity being removed by slightly redefining the problem (as mentioned above).
In another project, I was to write a server providing log reports. The initial (bad) idea, which I managed to veto, was to call this from an ASP application using some kind of custom COM control which we would have to write in addition to the ASP application itself. But since we ended up using HTTP we never had to write the COM component--it was already built by someone else and we could buy it instead of build it.
No integration problems, no development time, no debugging, no maintenance. Overall, less complexity for us to handle. Of course someone have to deal with the complexity (the component vendor), but if it's not on our radar anymore it's effectively gone.
Reply to This
Parent