Perl CMS: Development Experience
Disklamer: This article is written by XTreme. The person is not registered on Habré, therefore asked to publish article. What I am doing. If someone likes the article, I can give Mikhail contacts via drugs.
In the distant 90s, there were times when Perl was the most popular language for writing all sorts of "gadgets" for the then popular home pages. Actually, it was caused by a number of factors, but the fact was that on every second site where it was possible to install CGI scripts, it was possible to find a guest book or a bulletin board written in Perl.
')
Perl replaced the most popular PHP, and it was quite natural from the point of view that PHP has a much more understandable and intuitive development model. Both languages have their advantages - greater execution speed and security in Perl and ease of development and prevalence in PHP. But this question is rather a reason for the next “holivar”, so we will not go into it in more detail.
Most of the currently existing content management systems are written in PHP. This fact is indisputable, but it is caused more by the degree of the prevalence of a language than by the adequacy of the language to the task of creating a CMS.
I have been developing the Perl language management system for several years - initially for the internal projects of my studio, but at this stage the system has grown to the point where you can talk about the “public version”.
The CMS is called Taracot, and the project website is available at www.taracot.org (there is also a system demo). License - GPL.
From the main features of the system I would highlight:
- CMS is written in Perl and uses MySQL as a database;
- the system is designed for * NIX systems (Linux, FreeBSD, etc.), but can also be used on other systems, including Windows;
- the modular structure allows you to connect to your site any necessary functionality, in the main set already presented a large number of modules;
- works very, very quickly:
- quite comfortable and convenient user interface with the possibility of modification;
- “friendly” URLs;
- Some features of AJAX technology;
- safety (we hope;)).
The system is quite complicated to install on servers. This is caused primarily by the lack of support by Perl hosters - many necessary modules are not worth it, and it is necessary to correspond with the administrators regarding their installation. In general, this is a big misfortune of all modern projects.
Another flaw is bad documentation. Yes, since I am engaged in the project at this stage alone, I just physically do not have enough time to write the documentation competent. The same applies to a good installer.
Nevertheless, the system turned out quite successful in at least two plans. The first aspect is that the process of teaching users how to work with the system is quite simple (I managed to teach at least three people to work with it, who have almost no relation to computers and the Internet); The second aspect is not too much server load, which allows using CMS in large projects.
I hope that my CMS will be interesting and useful to many people, and especially I would like to appeal to the Perl community of programmers to pay attention to this project, point out and discuss shortcomings, and also take part, if possible, in the development.
Sincerely, XTreme.
UPD: The author of the article was invited to Habr, please love and favor - xtremespb .
In the distant 90s, there were times when Perl was the most popular language for writing all sorts of "gadgets" for the then popular home pages. Actually, it was caused by a number of factors, but the fact was that on every second site where it was possible to install CGI scripts, it was possible to find a guest book or a bulletin board written in Perl.
')
Perl replaced the most popular PHP, and it was quite natural from the point of view that PHP has a much more understandable and intuitive development model. Both languages have their advantages - greater execution speed and security in Perl and ease of development and prevalence in PHP. But this question is rather a reason for the next “holivar”, so we will not go into it in more detail.
Most of the currently existing content management systems are written in PHP. This fact is indisputable, but it is caused more by the degree of the prevalence of a language than by the adequacy of the language to the task of creating a CMS.
I have been developing the Perl language management system for several years - initially for the internal projects of my studio, but at this stage the system has grown to the point where you can talk about the “public version”.
The CMS is called Taracot, and the project website is available at www.taracot.org (there is also a system demo). License - GPL.
From the main features of the system I would highlight:
- CMS is written in Perl and uses MySQL as a database;
- the system is designed for * NIX systems (Linux, FreeBSD, etc.), but can also be used on other systems, including Windows;
- the modular structure allows you to connect to your site any necessary functionality, in the main set already presented a large number of modules;
- works very, very quickly:
- quite comfortable and convenient user interface with the possibility of modification;
- “friendly” URLs;
- Some features of AJAX technology;
- safety (we hope;)).
The system is quite complicated to install on servers. This is caused primarily by the lack of support by Perl hosters - many necessary modules are not worth it, and it is necessary to correspond with the administrators regarding their installation. In general, this is a big misfortune of all modern projects.
Another flaw is bad documentation. Yes, since I am engaged in the project at this stage alone, I just physically do not have enough time to write the documentation competent. The same applies to a good installer.
Nevertheless, the system turned out quite successful in at least two plans. The first aspect is that the process of teaching users how to work with the system is quite simple (I managed to teach at least three people to work with it, who have almost no relation to computers and the Internet); The second aspect is not too much server load, which allows using CMS in large projects.
I hope that my CMS will be interesting and useful to many people, and especially I would like to appeal to the Perl community of programmers to pay attention to this project, point out and discuss shortcomings, and also take part, if possible, in the development.
Sincerely, XTreme.
UPD: The author of the article was invited to Habr, please love and favor - xtremespb .
Source: https://habr.com/ru/post/49922/
All Articles