Thoughts, ideas, random notes, ramblings...

We have changed our Git branches around.  We have done this to help ourselves, and you as well.  The new branching architecture will help us get bug fixes out there faster and with less errors.

That's right, Fuel v1.0 is now officially available.  It has been 9 months in the making, and what a great 9 months it has been.  There has been a LOT of work that has culminated in 24,155 lines of goodness.

We have been kind of quiet lately, and there is a very good reason for that.  I (Dan) have not had internet at home for about 3 weeks now (besides iPhone tethering).  Work has been hectic, and I just have not had the time needed to properly attend to the Framework.  Fear not though, as the situation is being rectified this Friday.

It has been a little while (just over a month), but version 1.0 RC3 has been tagged and is ready for download.  This version fixes a lot of issues found in the previous release.  In total there have been 467 commits since RC2, so we have been hard at work.

This afternoon we were notified of a security issue with the Fuel Core.  We located and fixed a security issue.

This issue had to do with the URI not being properly sanitized, which caused a security issue in certain situations.

We have released RC2.1 and suggest that you upgrade immediately.

We have been asked many times about why we do this, or why we didn't do that.  Well, we have really good reasons for everything we do.  Let's start by going over our core philosophy:

Simple, Powerful, Lightweight and Fast.

Basically, this means we need to keep everything as simple to use as possible, while making it as powerful, lightweight (low memory usage) and fast as possible.  So, keep these 4 things in mind as we go through.

We know Fuel isn't fully compatible with proposed standards like PSR-0, but a framework is entitled to its own standards and conventions and we chose ours carefully. I'll explain below why the choices were made, but it's also important to know that our autoloader is very efficient. You can add any other autoloader on top of ours and once ours is done after 1 or even no filesystem checks the other one will kick in. Thus compatibility with PSR-0 is easily added without meaningfull overhead.

Yes, we use static classes. So that must mean the principle advantages of dependency injection are impossible right? Wrong.

Dependency injection is about making it possible to completely replace a part of the composition of objects that work together. To reach this goal you should never use "new Object" but always expect the new object to be given or set on your class.

The day the whole Fuel community has been waiting for is finally here. Only 4 months after its conception, Fuel RC1 is now released and ready to use! We're as excited about the RC1 as we will be about hitting v1.0, maybe even more so. Why? Because RC1 means that as far as we know it's all good. It means Fuel is ready to use and is approaching stability.

We have made a little change in plans...but in a good way!  We have gotten a lot of questions about when Fuel will be stable.  I have always responded with "soon" or "in a few weeks."  This was because we were unsure of what was left to do.  Well, now we have figured that all out and I have some exciting news.