Will the open sourcing of BD help Rails and others?
In case you missed it, BlueDragon (the J2EE version) is going open source as announced by New Atlanta earlier this week. This announcement has singled handedly fired up the CF community. I’ve been hoping for so that the Smith Project would take off and become the front runner of CFML engines since it was the only open sourced one at the time. Alas the project has been plagued with little enthusiasm from the CF community since it doesn’t support a lot of features and many just don’t want to contribute. BD on the other hand is feature rich and ready to go.
But let’s take and step back and look at what this could mean for other languages and frameworks out there. What could the other get from BD going open source?
For one thing, I’ve always wanted to just ditch CF and get into Rails, but there are some feature in CF that I just can’t get away from. I think the biggest is document generation with CFDOCUMENT. I can’t tell you how many clients I have using this feature to print invoices, attendee badges and other things. CFDOCUMENT makes it so easy to do. Trying using PDF::Writer in Rails to print an invoice, you’ll probably shoot yourself. This is one feature that the Rails community could look at and port into Ruby and ultimately include it in Rails.
Personally I think the open sourcing of BD was a very bold move by New Atlanta and will undoubtedly help get CF in front of more people. Kudo to Vince and the team for stepping up!
Can’t wait for the download.