And this is why we have <cfscript>
I disagree. Building CFCs in tags is the wrong approach for any number of reasons. Readability, for example. Being unable to program in any other language because you refused to use anything but tags is a big reason alone. Lines of code and less typing. I could go on. Tag based CFC’s aren’t just ‘a different way of doing the same thing’, they’re ‘the wrong way to do the same thing’. I’m sorry fi you feel otherwise, but that’s my opinion and I have good reasons for advocating that my fellow CFML developers drop tags like it’s 1999.
I already did. Do you have evidence to support your assertion that outputting tags directly is more performant than the savecontent/writeoutput/echo cycle? What kind of major performance boost do you imagine this would be?
IDE syntax highlighting is something that could be preserved by building a rendering pipeline using templates, or using React, or Angular, or… you get the idea. That said, I would have no problem with a html{}
function, if it were limited only to outputting non-evaluated (e.g. HTML/XML) tags. I could see a use for that in rendering templates, but for CFML tags it’s a no bueno from me for the reasons I’ve already stated.