Re:The growth of command line options, 1979-Present (2020)
by fsckboy on Wednesday December 15, 2021 @05:35PM
(#29572464)
ok sure, but unix is still here and perl died
there's a subtle thing about perl that's not mentioned often, which is how it borrowed ideas from many other tools and that made perl "intuitive" to learn for people who knew the other tools. But once you're embedded in just perl for awhile, you forget the other tools and then perl's grab-bag of borrowed ideas becomes sort of burdensome, it loses "intuitiveness".
Re:The growth of command line options, 1979-Present (2020)
by oblio on Friday December 17, 2021 @03:19AM
(#29589376)
Perl itself died. But Perl's philosophy of batteries included and do almost everything in a single language won.
If anything, Perl killed classic Unix and much of the Unix philosophy.
Every major modern design looks more like Perl than like Unix: Python, Ruby, PHP, JavaScript, Java, C#, Swift, Go, Rust, etc.
They're all "batteries included".
Re:The growth of command line options, 1979-Present (2020)
by AceJohnny2 on Thursday December 16, 2021 @03:14AM
(#29576167)
Only after I had to do some non-trival Bash scripting did I stop hating Perl's syntax. For one thing, at least Perl wasn't as bad as Bash. For another, I now understood where Perl came from!
Perl's syntax is a relic of its time, and it blazed a trail for what to do (and what to avoid!) in later scripting languages.
"Those days [of the Unix Philosophy] are dead and gone, and the eulogy was delivered by Perl."
https://interviews.slashdot.org/story/04/10/18/1153211/rob-p...