I am also an old style classic cfml coder since the 90ies (like some others
here), using really old cfml tags. My old CFML now works with Railo thanks
to its classic support, but now I really don’t know its future with Lucee
anymore. It really looks to me that the focus is shifting towards a new
language from now on, shifting away from CFML. By the way, I still use a
lot of .
Even if it is being said: CFML will mainly work and be supported with .cfm
on Lucee, now I know the teams focus will be on a new type of
LuceeScripting- or LuceeMarkupLanguage… so on the long run I understand
that I’ll have to recode my stuff into some sort of LuceeML just to be on
the safe side.
Do Lucee will attract new developers? Some for sure, but I will have to
rethink switching to ACF or even BlueDragon over Lucee. Why not Lucee?
Just a little example is the history of Railos documentation: There was a
documentation in Railo about Tags and Functions etc. But it was very
rarelly updated, rarelly complete, and poor in content. And it even was
offline or not working for a period of time… Yeah… Most of the time I
had to dig into ACFs documentation to look for functions and tag attributes
for railo, I even looked in Fortas CFs books. And how will that be with
Lucee? If Lucees docs will be like Railos, that will be a very tough start
to attract new developers. ACF docs complemented Railos a lot and that gap
will have to be filled.
Another example was the installation: I remember when I’ve tried to install
Railo for the first time… it was 3.x on a WIN machine with IIS, and there
wasn’t any installers or docs about it. It was a real pain to make Railo
work. Fortunately there was an outside blog post that someone of the railo
community made and linked to. And even with Railo 4.x it is still a pain
making it work on WIN and IIS.