Initial Impressions of Fusebox 4

Today was the day I finally sat down and started doing more than just poking around at the Fusebox 4 core files and demo applications– I actually decided to use it.

It did take me a bit to get used to the way that you now map out circuits, but given that I’ve only played with it for 8 hours now, I feel like I already have a strong grasp of how it works.

I originally mapped the application out similar as I would of had I been doing it in Fusebox 3, but given all of the powerful new stuff, it seemed way too clunky. By the end of the day I found myself moving everything into an MVC based architecture.

One thing that is good and bad is that you really have to put a lot of design time into your application. Its not as easy or obvious to do things such as decide what a default fuseaction is based on if a user is logged in or not. Since you can’t put conditional statements within the Fusebox and Circuit XML files. However, I’m a big fan of lots of upfront effort instead of cobbling something together quickly, so it helps you stay true to your software development background, instead of giving into those deadlines that people not involved with the process of development always put over your head. ;)

Other than the time it takes to get used to the new XML configuration files and debugging all of the newbie errors, I dig it. I know there are some big fusebox pundits out there, and for me its not a holy war. It works, a lot of people use it, and it allows me to concentrate on developing applications instead of frameworks that I end-up not liking 6 months down the road. Anyhow, try it out for yourself and form your own opnion. :)

This entry was posted in Frameworks, Languages and tagged , , , , , , , , , , . Bookmark the permalink.

Leave a reply