Nobody really gives a shit about this kind of stuff, but here it is, a full historical breakdown of the technology powering jargon.
Any release date with an asterisk means I'm totally guessing, as I didn't have a proper change log.
|0.1||1999-09-12||A static page with a single image.|
|0.2||1999-09-15||A static page with four images on it.|
|1.0||1999-09-17||The first jargon engine was a horrid hackish Perl script. It was horrific, with its own god-awful configuration format for storing the strip details in.|
|2.x||2000-04-01*||The second jargon engine was the 1st release of the Gallery plugin for my Webtoo Websight content management system. It also had a horrid custom configuration format, that was hideous to try to maintain.|
|3.x||2001-09-15*||The Gallery plugin got a complete rewrite. The new version used YAML for it's configuration format. It wasn't perfect, but it was world's better than what had gone before. This version would receive the most updates, including a few that probably counted as near rewrites, but as the data format, core plugin infrastructure didn't change, I counted them all as 3.x.|
|4.0||2010-12-28||A standalone CGI based engine written from scratch, still using the existing YAML data, but using Modern Perl 5 components, and the Petal template engine.|
|4.1||2011-06-22*||I refactored the 4.x codebase as a more flexible PSGI application.|
|5.0||2014-05-02||A whole new engine written from scratch using PHP 5.4 and my own Nano micro-framework which I've used in a few other projects. I finally dumped the YAML file, and now am using MongoDB for strip and chapter storage.|
|5.1||2016-02-01||Ported to PHP 7.0 with the new MongoDB driver and client library instead of the older mongo extension. The new driver and client library are much cleaner and use PHP namespaces like the rest of my code. This update was introduced Feb. 1st, 2016.|
From version 1.0 to version 4.0 I was using Apache as the front-end web server and CGI as the application connector.
From version 4.1 onwards, I'm using nginx as the front-end web server with FastCGI as the application connector.