Stories
Slash Boxes
Comments
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

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • ... people seem to be so intent on tossing something together as quickly and inexpensively as possible that they don't consider the long-term issues they may be causing.

    In the past, people also wanted something done quickly and inexpensively, but two factors made the difference in the old mainframe programs you saw.

    First, the economics were different when those programs were written: computer time cost more than programmer time. It behooved people to get the most out of their allocation, so they set u

  • At least they didn't sue you for pointing out the security issue :/

    -matt
    • I had briefly considered that possibility. I had noticed that the data I sent had a typo and I was tempted to have fun by fixing the typo myself by creating an account, but that would have been pushing my luck :) As it stands now, they have incentive to keep me happy and I did not compromise their system. Fortunately, I have better luck than merlyn.

  • I think the choice of technology says a lot about the company - if they are using ASP then they care more about following the crowd and ticking boxes than actually thinking.

    I have worked with ASP for over a year and can safely say that server-side validation is the exception rather than the norm.

    Worse still even if you do server-side validation, you can't control what happens when you call COM objects that are required for even basic tasks like email, file uploads and browser detection.

    It is possible

    --

    @JAPH = qw(Hacker Perl Another Just);
    print reverse @JAPH;