Why and How Was This Framework Created?

This framework initially grew out years of frustration while working with extremely slow monolithic popular frameworks and the style of inept developers they have brewed, then became an exercise in what can be achieved if quality and efficiency are used as fundamental building blocks.

What were its goals?

The main point, evident from drawbacks of frameworks I worked with, was finally building something that is extremely fast (as close to php raw as possible), extremely simple to use, but at the same time with easily extensible architecture, allowing developers to plug out functionalities their sites do not need or the opposite, adding their own contributions. This way the completeness popular monolithic frameworks can boast with is achievable with minimal performance loss because framework continues to never do more than absolutely required.

What were those goals met?

Standing on an aesthetic foundation, framework ended up as integration tool of pluggable functionalities assembled into independent APIs, each dedicated to an aspect of a web application's logic. Framework is the ultimate assembly unit that works like a web application skeleton onto which developer assembles his code in order to have a fully working site. Thanks to this design, it naturally achieved unparallelled:

Lucinda Framework maintains simplicity of design (setup is done mainly in XML) and also makes sure no logic that is not explicitly needed will ever be ran. Taken together with absence of dependency injection container (a massive performance killer in all frameworks) and general adherence to aesthetic perfection principles, it predictably outperforms (in terms of both speed and ergonomics) any other true framework written in PHP!


Share