This is my opinion too.
Spending my time with PHP these days, I’m only ever doing PHP in the backend code (the M&C of MVC)… we use Twig for the views. We literally can’t use PHP in out views!
I think this is a good approach, and makes for better code and separation of concerns. However I think the structure of CFML’s (and so: .lucee’s) tag-based functionality is an even better fit than Twig’s {% %} approach, so it’s OK to stick with tags.
One of the more fruitful Iris topics we discussed was exactly how few tags Iris should have. It wasn’t many (it’s all in that spreadsheet floating around). I think this should filter through to .lucee.
It’s the sort of change that might irk some old CFMLers, but they’re probably not likely to move from CFML anyhow, so might not be much of a consideration.
–
Adam