Ray has an interesting post where he used CF8's new cfthread and cffeed tags to create an RSS aggregator. Slick. Towards the article's end, however, he says, "I'd love to see the same code written in PHP. No external libraries allowed - it must be all "baked in" code."
Which got me thinking. Do we really want everything "baked in" to ColdFusion?
Lynch Consulting has an interesting project going on: a centralized caching solution for ColdFusion servers using the open-source project memcached. It, along with the comments that follow the article, provide a good discussion of the pros and cons of using a centralized server in multi-server environments.
The previous article which asked "Is ColdFusion still relevant" generated some interesting replies and emails, including a thoughtful and well-reasoned comment by Adrock from Adobe's ColdFusion team regarding its future.
One part stands out, in which he says, "Personally, I'm seeing new ColdFusion developers/customers coming from two new places. Companies moving towards Flex/Apollo choose ColdFusion as the logical middle-ware and enterprise Java shops who are just now coming to terms that enterprise Java development isn't the best fit for departmental smaller applications."
This, to me, says that ColdFusion growth is being driven in more of a "top-down" fashion, dictated by management's decisions and choices, as opposed to the "bottom-up" grass-roots popularity more commonly associated with the open-source movement.
CFInternals will be a look inside advanced ColdFusion website development and best practices, with an emphasis on designing and implementing object-oriented systems and frameworks, object-relational management systems (ORMs), and content-management systems (CMS).