portal entry

Beeing a CF developer for 20 years and a C# developer for 10 years I must say your selection of comparison points is very limited and very biased (which was to be expected from a dying platforms promoter). What about runtime performance. What about security (CF is Java based - did you forget that when mentioning the .NET framwork? LOL. And my user account got hacked from Adobe, not from MS ;-) ). What about community support. What about IDE. What about longterm maintainability of large code bases. What about quality of support and speed of reaction. What about licensing. I could go on and on and on.

Comment by tomfaller

If this article was intended to be inflammatory, then congratulations - you have succeeded. I get the impression that you have not done a large amount of work with ASP.NET or C#. Keep in mind while reading this: I do still think CFML is a good choice, but so is ASP.NET. I currently use both, and I enjoy using both. However, I will stick with Lucee CFML vs Adobe. I have not used Adobe CF in a few years, but the last time I was involved, it was not possible to include only the parts of CF that were needed. C# makes it easy to only include what is needed (using statements). Lucee is also more modular now, so it is easy to leave out the parts of the framework you do not need. Ease of use: Yes, C# is definitely more complex. This does have some benefits, such as being strongly typed, which I do prefer. PDF Support: Again, I'm not sure where Adobe CF is now, but in the past the ability to create pdf documents existed, but it wasn't particularly pleasant, and you were required to include the functionality whether or not it was being used. Lucee removed the pdf library from the core, and it is now easy to add on if needed. It is easy to include PDF capabilities in C# - there are quite a few free to use pdf packages that can be added to ASP.NET. Having a choice also gives me more control over how I want to manipulate a pdf. Other document types are also not difficult to manipulate. Operating System Limitations: Please see .NET Core Security: Really? All that aside, every language offers you the chance to be insecure. Implementation is the key. OOP: I get the impression that you are stating that ColdFusion invented OOP. While I can't be bothered to look up the facts, this seems unlikely.  

Comment by themikehenson