So that is the question to explore in this topic… what does everyone think?
The general argument for a namespace is that we would need a namespace in the tag syntax to differentiate the “Lucee” code from the HTML that will surround it, because of course you will only use tags in views, otherwise in the future the HTML specification might add a new tag that conflicts with one of the Lucee tags and the namespace protects from this. However personally I don’t like the colon, to me it just looks and feels awkward. Take for example:
<cfif a EQ b> <cfset c = d> </cfif>
<:if a EQ b> <:set c = d> </:if>
I’m not sure if it is just I find the first familiar and the second not but the colon is just not feeling right to me. Particularly on the closing tag for some reason where you have both the slash “/” and the colon “:”. Now removing the namespace all together, e.g.
<if a EQ b> <set c = d> </if>
Looks and feels very nice and I think that without the namespace you could do some clever stuff, e.g. you could define an override for an HTML tag, e.g. the img tag:
<img src="/images/myimage.jpg" width="50" height="50" crop="center center" resize="true" maintainaspect="true'>
And if myimage.jpg was say 500x250 it would resize the image to 100x50 (maintain aspect) and then crop it around the center and return a 50x50 image in an html tag:
<img src="/whatever-temporary-source-file-is.jpg" width="50" height="50">
However if you had just:
Then Lucee would just ignore this as it is clearly just HTML with no additional arguments for Lucee to interact with.
You could do all sorts of dynamic HTML view layer things like this then. This to me would be a good argument for not having a namespace in the Lucee dialect.