Why do corporations hate perl?
The organizers of the YAPC :: Europe conference announced that the main theme next year will be the use of Perl at the corporate level. Or rather, the problem of what to do with the enormous volumes of poor-quality code that have accumulated over many years.
Dave Cross , a technology developer and journalist, has been creating Perl corporate systems all his life, attending the aforementioned conference, where he spoke with company representatives. He writes on O'Reilly ONLamp's blog that he himself could have announced next year with a report on the topic “Why Corporations Hate Perl” . This is really unfair, says Cross.
Dave Cross is not worried about his own future as a programmer, because until his retirement he can be provided with work, supporting many of the systems he has already created. However, the fact is that many large companies are now abandoning Perl and are going to rewrite everything in Java + PHP.
')
At present, the developers of the web systems themselves are clearly beginning to treat Perl as one technologically obsolete artifact and, on the whole, speak disdainfully about it. This mood is transmitted to customers who do not understand the technology, but now they immediately start worrying when they barely hear the word “perl”. They do not need "outdated" solutions, they want beautiful systems on new technologies.
Dave Cross acknowledges that in ten years companies have accumulated a lot of poorly written Perl code. But its poor quality is not due to the technological imperfections of Perl itself, but by completely different reasons. In fact, developers worked in an environment where quality was not a top priority. Many projects were the first steps of companies in the field of web development. Naturally, the quality of the projects was not up to par. Created by individual units, these systems often could not even exchange information with each other. Not surprisingly, maintaining this code is now a difficult task.
On the other hand, there are many examples when a modern system is created in Perl, and it performs well: it is easy to maintain and refine. Here Perl is not inferior to any newfangled language.
Certainly, companies have accumulated a lot of code that needs to be rewritten over the next few years. However, the transition to new languages ​​is too radical a measure. Executives blame Perl for the problems that are actually explained by management mistakes and the wrong approach to development.
Ten or twelve years ago, almost all of us created Perl applications and we all made mistakes. Now we have to correct these errors. But over the years we have become more experienced and now we can rewrite the system, taking into account all that we have learned over the years, writes Dave Cross.
The hardest part is fixing Perl's reputation.
Dave Cross , a technology developer and journalist, has been creating Perl corporate systems all his life, attending the aforementioned conference, where he spoke with company representatives. He writes on O'Reilly ONLamp's blog that he himself could have announced next year with a report on the topic “Why Corporations Hate Perl” . This is really unfair, says Cross.
Dave Cross is not worried about his own future as a programmer, because until his retirement he can be provided with work, supporting many of the systems he has already created. However, the fact is that many large companies are now abandoning Perl and are going to rewrite everything in Java + PHP.
')
At present, the developers of the web systems themselves are clearly beginning to treat Perl as one technologically obsolete artifact and, on the whole, speak disdainfully about it. This mood is transmitted to customers who do not understand the technology, but now they immediately start worrying when they barely hear the word “perl”. They do not need "outdated" solutions, they want beautiful systems on new technologies.
Dave Cross acknowledges that in ten years companies have accumulated a lot of poorly written Perl code. But its poor quality is not due to the technological imperfections of Perl itself, but by completely different reasons. In fact, developers worked in an environment where quality was not a top priority. Many projects were the first steps of companies in the field of web development. Naturally, the quality of the projects was not up to par. Created by individual units, these systems often could not even exchange information with each other. Not surprisingly, maintaining this code is now a difficult task.
On the other hand, there are many examples when a modern system is created in Perl, and it performs well: it is easy to maintain and refine. Here Perl is not inferior to any newfangled language.
Certainly, companies have accumulated a lot of code that needs to be rewritten over the next few years. However, the transition to new languages ​​is too radical a measure. Executives blame Perl for the problems that are actually explained by management mistakes and the wrong approach to development.
Ten or twelve years ago, almost all of us created Perl applications and we all made mistakes. Now we have to correct these errors. But over the years we have become more experienced and now we can rewrite the system, taking into account all that we have learned over the years, writes Dave Cross.
The hardest part is fixing Perl's reputation.
Source: https://habr.com/ru/post/38014/
All Articles