Today we held a developer's review of the work being done in the trunk for the release of ImpressCMS 1.3, and while we talked a lot about the approach Marc and I took for this project, the real benefit shows in the benchmarks we have comparing 1.2.2 and the latest revision of 1.3. The greatest amount of effort has gone into the new architecture for the classes used by ImpressCMS - consolidating duplicate files and functions into single classes and separating each class into its own file. This has been a rather comprehensive work, because no one has done this in any other project before ImpressCMS - none of them have taken the time and made the effort to create a unified code base for their project.
We didn't do this just because it would make us different than the other projects or to break compatibility with previous versions, we did it to gain better performance, more stability and more scalability. We are in a time where most people have access to the Internet through a broadband connection, but also at a time when more people are browsing the Internet using mobile devices - those devices are not using broadband connections, so sites built on ImpressCMS, or any other platform, must be optimized for viewing on devices with less than highspeed connections. We also want to be considered for enterprise-level sites, where high traffic is normal and performance is an issue. So, we need to be critical about what code is included in our core and how well it performs. Let's have a look at how the numbers are stacking up, shall we?


I have already been in Chicago for 2 days now for 





