Sunday, April 06, 2008

Why Adobe should LOVE Open BlueDragon

Friday I let the cat out of the bag about one of the cool features of Open BlueDragon, Sandbox Projects. Prior to this Jason Delmore had a very informative post explaining why ColdFusion is not free. Jason begins by stating ColdFusion is not a lot of things, failing to really tell us what ColdFusion is in any certain terms other than a platform that does not fit the mold of all the things it is not. He conceeds that ColdFusion the language is free, or rather agrees to call it free for the sake of conversation, "let's call this FREE." Jason then proceeds to describe a bunch of features that cost oodles of money if developers/organizations want to use these technologies. Adobe seems to be very enamored with creating the "ColdFusion platform," and why not its a great revenue machine. This is EXACTLY why they should love Open BlueDragon. Think about sandbox projects for a second. If the language itself is a small part if ColdFusion why bother maintaining it? Why not let the community support the language, while you (Adobe), and others, focus on the platform. If Adobe thinks their exchange integration is popular enough test the waters make an extension pack for Open BlueDragon and put a price tag on it, likewise for the ajax features (though I would love to see that one GPLv2 so it can come bundled). One thing I did not cover in my last entry is how you can even override default behaviors with Sandboxes. Thanks to this type of behavior Adobe could even offer their cfImage enhancements as an alternate package. The community would really prosper from this type of business model. CFML becomes a powerful community driven language by itself and the platform can be grown by multiple companies that add value to the platform (or language) through extensions (humm sounds like my favorite IDE!!).

2 comments:

Ben Davies said...

That is gold.

I've never downloaded or used Blue Dragon but your previous post regarding the 'sandbox' code branches sent a shiver down my spine, because ultimately thats exactly what I want for CF - An extensible platform and a community driven language.

In fact I came back to your blog to find your original post, because I was about to say the exact same thing on Jason's blog on the exact same post.

Adobe can't continue with business as usual, IMHO.

ike said...

Also sounds a lot like what I hope for with the onTap framework community. :)