There are two main reasons why you would look at using Micro-Frameworks. The first is to give you functionality which your main framework does not provide. Here you would use it in addition to your main framework. The second is if you feel that the cost on performance of using a large library, which provides a range of functionality, is too high for the benefits it gives you. Perhaps you only require a small subset of the power it provides. With the performance of websites being an important factor in retaining customers it’s natural that developers are looking for ways to reduce the amount of code loading to improve page load times. In this case a micro framework or combination of micro frameworks to create a custom framework might prove the best solution.
When selecting a Micro-Framework for either reason a developer must remember to consider all of the factors they would normally look at when selecting a framework. These include:
- The number of people working on the framework. Typically you want a number of people to be developing it to increase the chance of the framework continuing to develop and mature.
- The stability/level of testing. This is especially important in a corporate project. You need to have confidence that each release is well tested and won’t introduce bugs into your application.
- Cross Browser support. You need to have confidence your site will behave/appear correctly across browsers.
- How active the community is behind it. This can impact on the longevity of a framework, the level of documentation and support.
- Placing the references to your scripts at the bottom of the page.