4 ms·
> I think YOUR perception of Perl is what is outdated here. Next to no one uses Perl any more. You won't find people to maintain your homegrown stuff - and asi
by mschuster91 10y ago
> I think YOUR perception of Perl is what is outdated here.
Next to no one uses Perl any more. You won't find people to maintain your homegrown stuff - and aside from maintaining an OTRS instance I have not seen Perl code in a decade.
> Most things can be done in 1/10th of the LOC and OOP etc won't matter when your Bash script is one file and 150LOC instead of 5-10 files, objects an methods that are called just one time etc, 1000+LOC PHP.
Well good luck with Bash if your batch script involves stuff like parsing JSON/XML or interacting with databases. I prefer to write quick one-offs in PHP than wasting hours with Bash scripting; and even if it's no one-off but a script that needs to be run regularly (e.g. via cron), you'll find a competent PHP programmer for maintenance way easier than a competent Bash programmer.
> And come on, for "job control" type scripts you should be fired for using PHP over Bash.
For plain job control, like an initscript, I fully agree with you. But not for anything more complex, for the reasons outlined above.