With WebGUI, It's In There
In a recent interview I did with SourceForge, I got to plug all the really great development that's been going on in the second age of Perl.
I think it's nice when we as Perl devs are able to spread the word out to audiences outside the Perl community. Hence the reason I share this link. I'd like to see more of this from other Perl devs.
My little part in the greater Perl world.
With WebGUI, It's in There, unless by It you mean support for databases other than MyISAM MySQL.
In their roadmap they recommend moving away from feature-anaemic MySQL and suggest PostgreSQL as a possible solution, but essentially dismiss it since '... it's so different from what we use currently that it would likely get killed in the mire of work it would create to switch to it', which is a damning statement, considering that WebGUI actually started out with multiple RDBMS support but seem to have adopted MySQLisms wholeheartedly to the their, and others, detriment.
The work they would have to do to switch away from MySQL is the fault of their strong and enthusiastic dependence on the lowest common denominator database system.
An interesting counterpoint to this is Bricolage, which for years seemed very tied to the PostgreSQL DBMS, but now runs as well on MySQL as it does on Pg.
My post isn't actually about WebGUI, it's about the promotion of Perl outside the Perl world. However, since you appear to quite angry about this particular topic I feel it's only right to offer a counter point.
1) If WebGUI's prereqs don't support the database of your choice there's no reason to be angry about it. Just use something else.
2) As I said in my article, we once supported both Oracle and Postgres in addition to MySQL. We did this for three years. During that time we got exactly 3 people using Postgres and 1 using Oracle. We got over 10,000 using MySQL. We're a business. Do the math.
3) WebGUI 8 moves the default storage layer to InnoDB. We evaluated Postgres as a possible database, but then we looked at our historical experience with it, which wasn't good. In addition, the 10s of thousands of deployments we already have use MySQL, which means migration for our users will be much easier if we simply switch to a new storage engine inside of MySQL.
I'm sorry that you somehow feel we've wronged you by excluding Pg. There is certainly a very small minority in our community that wishes we also supported Pg, but they don't get angry. They either decide that WebGUI is worth using MySQL, or they move to a CMS that works on their database of choice.