Comment Speedy code changes (Score 1) 432
At the corporation where I work, we frequently choose script over compiled code for a myriad of applications. Since we have 24x7 systems to maintain, rapid error recovery is vital. If I get a call at 2:00AM and drive in to the office, when I identify the offending program, I want to be able to fix it on the spot without having to dig up a particular development environment. With script, Vi or notepad is all I need to solve the problem and get back to sleep.
The complaint with script of course is speed. In comparison to compiled code, it dogs. In our environment we do worry about performance tuning, and look for obvious inefficiencies like everyone else. But the simple reality is: "Too slow? Buy a bigger box". In the grand scheme, hardware is cheap, people are expensive. Therefore, we script. It gets the job done and frees us up to get to other projects.
The complaint with script of course is speed. In comparison to compiled code, it dogs. In our environment we do worry about performance tuning, and look for obvious inefficiencies like everyone else. But the simple reality is: "Too slow? Buy a bigger box". In the grand scheme, hardware is cheap, people are expensive. Therefore, we script. It gets the job done and frees us up to get to other projects.
