Saturday, November 14, 2009

FuseNG and therefore Fusebox by default are dead...

A few months back I tweeted that anyone can build a framework in CF; what we need is more good software out there. Given the choice between maintaining a framework and listening to the nagging whining community or developing an open source application and listening to nagging and whining community I'll take the application. My heart is just not in FuseNG, or any other framework, and I can't hold onto the framework to make people happy or ensure it has a support person. That's just not what I want to do.

For those that thought it would never get off the ground congratulation you were right! To those that had new hope for the future of Fusebox, sorry FuseNG will not be it for you. You see over the past year my career has change drastically. I do not officially work on ColdFusion at work any longer and I never find myself in the situation where I am using Fusebox. I can not continue to develop a framework I don't use, it will stagnate. I hope someone else in Kroger will step up and take on Fusebox or revive the FuseNG fork, but that is up to the other individuals that originally looked to me for leadership of FuseNG. As much as I am sure some of you would like to leave feedback or comments I'd rather not open the potential for flames so comments are off. If you really must share your opinion feel free to email me.

FuseNG is dead and Adam was the one that said it. I totally get where Adam is coming from. If your heart is not in it then it is not something to not pursue. Our lives are short. Best of luck to you, Adam, with your new management career.

I truly believe that FuseNG was the only hope for Fusebox as I do not see much involvement from the current maintainers of Fusebox. Maybe somebody will swoop in and save FuseNG, but that would require a long term framework vision and big time commitment. Only time would tell...

I totally agree with Adam that the CFML world is missing really powerful, enterprise level, commodity applications that extremely mature and polished. I think the downfall as a community as a whole is we think about building new tools, but not full-blown open source applications. Sadly, other development languages like PHP are littered with big name applications that make it into the headlines. They have a huge head start on us (we're talking many years) in the terms of maturity and polish.

One thing we are not missing in the CFML world is a selection of frameworks. So jump on in; the water is warm! Just one word of advice, do not use this as an excuse to build yet another framework in CFML. You're just re-inventing the wheel with different paint or materials. Your time would be better spent (yours and everyone else that benefits from your time) by becoming involved with an open source framework / application by adding to the spit and polish of that chosen project. Think about the CFML community as a whole instead of scratching that "I think I can do it better in my own way" kind of itch.

Please no flames... (and yes, I think I can now be crowned the "X is dead..." king for those who have been around for long enough).


  1. Interesting timing on this post--this is the "other side" of this issue:

    Chicken and egg to be sure, but I wonder how much of that goes on that we don't see on blogs, etc. That tide needs to be stemmed as well.

  2. I think that bundled WARS for something like StatusNet would be awesome for people that are married to the Java platform already. I think that this is best place for CFML as a language to make a break through in. It appears that a StatusNet like application is an under served sector of the application market across all languages. For larger to medium companies, I'm sure it would be really nice to have an internal "twitter"-verse.

    I think if any effort goes into a new open source apps for CFML -- I think that StatusNet might be a great leader for us as a language. Any open source application built for CFML needs to be unique to bring in new developers.

  3. I thought I continue on a reason why it's easy to say that Fusebox is dead at the moment. Consistently, CFML frameworks have revolved around one main contributor without building community. So unless an author can pass the baton to a new steward -- the framework will just die due to the lack of stewardship. This is where Mach-II is changing -- our core team recently doubled from three to six team members and we are focusing on building a community not just a great framework.

    I am curious if Fuseboxers will step up and support their own framework for the years to come, but at the moment nothing concrete has surfaced in regards to organizing. Again, this is where a strong community who have had previous involvement can just step in easily.

    Personally, I don't think anybody going to swoop in and save it for the long term. If somebody does, a word of advice is to make sure you build a community. Otherwise, the fate of a project rests on one person or a few people alone. We all do need breaks from things -- even the things we love dearly -- that is why a small contributor to user ratio is actually detrimental to the project. I hope the Fuseboxers can prove my blog post title irrelevant in the months to come. I will happily eat my words!