Slashdot Mirror


Do Scripters Suffer Discrimination?

TheTheologian writes "In his InfoWorld column, Chad Dickerson says 'there is a level of quiet discomfort between the "scripting" versus "programming" factions in some corporate development environments in which I have participated. In some instances, executive-level technology management has held scripting languages in disdain as not being "real" languages for day-to-day problem solving, which has discouraged highly talented scripters on staff from practicing their craft. In such an environment, scripters are relegated to the lower ranks ... ' He goes on to say that some companies will assign Java and C++ programmers tasks that take them weeks but could be done by Perl or Python programmers in a few hours. Is it true that some companies are so overcome with code bias they'd assign weeks of unnecessary work rather than give it to the scripting untouchables?"

10 of 1,044 comments (clear)

  1. Score 5: Funny by Anonymous Coward · · Score: -1, Flamebait

    Yes. Because their fg8s.

  2. Score -1: Idiot by Anonymous Coward · · Score: -1, Flamebait

    Weakest...post...ever. Seriously, dude, are you like 12 years old or something? Sheesh.

  3. Script languages are for cut&pasters anyway by Anonymous Coward · · Score: -1, Flamebait

    Wannabe a programmer? Just learn how to cut and paste CPAN perl code.

    Learn to cut and paste or learn to program. Perl is for the cut and pasters.

    So many perl support mailing lists are cluttered with questions like where can i find a program that sorts this or writes that?...

    Cut and pasting is not programming.

    I want to maintain complete control over my programming environment. C rocks. Perl sucks.

    There is an abundance of perl code available.
    If your desire is to become a cut and paster.

    Learn to program
    or
    Learn to cut and paste perl.

    Ask a c programmer what his program really does. He can tell you.

    Ask a perl paster what his program really does. Chances are he might be able to recite perl syntax.

    If you are one of the masses, go with perl.

    Its easy and requires less work.

    Wannabe a programmer or a paster?
    Its your call...

    1. Re:Script languages are for cut&pasters anyway by Anonymous Coward · · Score: -1, Flamebait

      Look, I just got something done without spending a bunch of time on it:

      Wannabe a programmer? Just learn how to cut and paste CPAN perl code.

      Learn to cut and paste or learn to program. Perl is for the cut and pasters.

      So many perl support mailing lists are cluttered with questions like where can i find a program that sorts this or writes that?...

      Cut and pasting is not programming.

      I want to maintain complete control over my programming environment. C rocks. Perl sucks.

      There is an abundance of perl code available.
      If your desire is to become a cut and paster.

      Learn to program
      or
      Learn to cut and paste perl.

      Ask a c programmer what his program really does. He can tell you.

      Ask a perl paster what his program really does. Chances are he might be able to recite perl syntax.

      If you are one of the masses, go with perl.

      Its easy and requires less work.

      Wannabe a programmer or a paster?
      Its your call...

  4. Re:Right tool for the job by Jeremy+Erwin · · Score: 0, Flamebait

    A good programmer who knows his perl may be able to replace a lengthy C/C++ program with a few lines of perl, but what happens when that programmer moves on?

    To the untrained eye, perl looks like line noise, and may be rather difficult to maintain. Admittedly, perl is rather popular, but suppose that a programmer decides that lisp, haskell, or intercal is apropriate to the job at hand?

  5. here's why by b17bmbr · · Score: 0, Flamebait

    you wanna pick up somebody's perl code (or even your own) six months later?

    --
    My problem? I was perfectly gruntled, until some numbnuts came by and dissed me.
  6. YHBT by Anonymous Coward · · Score: -1, Flamebait

    HAND

  7. Holy Fucking Gator Shit Bitch by Glonoinha · · Score: -1, Flamebait

    Ron Harwood you evil nasty motherfucker. Shit piss I just went to your PHP based tradewars blacknova page to check it out, even bookmarked it, read a little of the faq and THE MOTHERFUCKER TRIED TO INSTALL GATOR ON MY ASS.

    Dude you completely suck major dick.

    If any spiderbots are looking, please explain to harwoodr@linux.ca that GATOR IS FUCKING BULLSHIT SCUMWARE. I can not believe that a /.'er would have a drive by GATOR installation on his fucking front page.

    Now I have to figure out how to tell /. that I hate you. I honestly can't believe how much you suck dick - you are right in there with the telemarketers and spammers - even worse because you come into our home here on /. and try to join our conversations. Pigfucker.

    --
    Glonoinha the MebiByte Slayer
  8. Re:PHP scripting/coding/whatever by darthwader · · Score: -1, Flamebait

    As someone who's spent several years managing programmers, I can tell you this: the number one cause of bad programs is poor programmers. I find that good programmers write good code, regardless of the language. And bad programmers write bad code, also regardless of the language.

    Now, to give you some ammo for your religious war: Strong typing is for weak minds. If your friend doesn't have the mental decipline to keep track of his types, he's welcome to use the Java compilier as a crutch to do it for him. If you know what you're doing, you don't need any smart-assed compiler trying to tell you what you're doing.

    --
    I hate it when I make a joke and I get modded "+5 insightful". Mod the stupid comments "funny", not "insightful", pleas
  9. Re:PHP scripting/coding/whatever by sdhascrappyacctmgmt · · Score: 0, Flamebait

    First, I would suggest that [long winded arrogance] means you either didn't listen to or didn't understand what your friend was saying. And PHP's short path to hell is not loose types, but its' (early versions, mind you, and therefore most of the installed base) over-reliance on GLOBAL FUCKING VARIABLES. This can be the short path to hell with Perl, too, which is why we have the "use strict" pragma, as well as locals.