I hear alot of arguments (particularly of late on the CFAUSSIE mailing list) about ColdFusion and Object Oriented Programming.
It seems that almost even the most tangential conversation that could possibly relate to OOP, degenerates into pointless bickering about how OOP is good, bad or ugly when combined with CF. It's verging on rediculous.
The facts remain as such – Object Oriented programming has been THE software development paradigm for more years than I have been alive. There is a REASON why we don't code in procedural code anymore, and a REASON why Object Oriented programming has come into almost every aspect of software development.
Looking solely at Macromedia related products. CF was procedural, and then came along CFC's. Flash was… well, Flash… and now you can define classes in Actionscript. Blackstone will further enhance CFC's with Event gateways and the like.
The truth of matter is – the Future for Coldfusion IS OO. You can like it, you can hate it, but quite frankly, if you develop with CF, Object Oriented programming is here to stay, and there is nothing you or anyone else can do about it. All it's every going to do is infiltrate more and more of the CF development community, as the years go by, and the support for it in future ColdFusion versions grows.
Yet again, I implore you – if you want to develop your software development abilities with ColdFusion go and drop into a Java course. Not only will it give you the theory you need to stay with the time in ColdFusion, but it also provides you with the ability to combine CF with it's sister language, and give you capabilities with this language you never had before.
Can that really be a bad thing?