Virtualization is very useful for application isolation. Bare metal doesn't work for most applications; the cost in hardware overhead is high and the utilization is often sub 10%. Yet the application must be isolated from other applications for security or configuration reasons. Some things run better on bare metal, but the datacenter cost can be very high for medium to large companies.
Perl is very much a write-only language for most programmers, and even many Perl programmers. If the average coder has to mentally parse several sigils, matrix that with context, and then look deep into a subroutine to see what is done with a variable, it's not a good thing for the programmer. It can be done, and I'm sure those who live and breathe deep Perl on a daily basis can mentally parse things much faster. Most of us can't do that. We can parse things in our spoken language because we have lived in it for years. Yet we still miscommunicate and misunderstand. We spend hours trying to find some way to write a test for some undocumented subroutine that's a hundred lines long and heavily interdependent with other subroutines that make no more sense than this one.
Your post makes me think you're a skilled Perl programmer. Perl is a great language that can solve a lot of issues. The more we understand why "they" are making choices we feel could be done better, the more we can help them see why Perl might be a good fit for them. You have the ability to solve a lot of problems with Perl, probably moreso than many of us.
In reply to Re: Why Perl in 2020
by Leitz
in thread Why Perl in 2020
by ait
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |