Allow me to introduce myself. I’m WolfShade, and before I started learning CF, I was a PC tech and network admin.
I have been a ColdFusion developer since 2000, and I absolutely love it. I have a passion for CF coding.
My boss has recently tasked me with researching Lucee, so I thought that this should be my first stop.
I am looking for all of Lucee pros and cons so that we can present it to the higher ups in an attempt to replace ACF with Lucee. Trying to convince them to switch will not be an easy task. If you have any references (articles, whitepapers, etc.) that will drive the point home, that would be all the better (the higher ups will require proof of any statements.)
I look forward to meeting you, and socializing, and helping, and asking for help, and…
The fact that Lucee is open sourced provides many benefits.
A simple way is to write your own custom tags and replace the old tag calls with those new tags, which is usually not a huge task, and when you compare the cost of adapting your applications to the cost of ACF licenses it’s usually much cheaper to refactor your apps.
I’m not sure if we have a complete list of incompatibilities anywhere, but it’s something that we discussed many times and at least a partial list should be available somewhere (need to find it, maybe someone else here can point to it).
Hello, @21Solutions, thanks for such a quick reply.
The higher ups are wary of open source. Those of us whom are tech-savvy understand it; they won’t. That’s part of the problem with pitching this idea. The idea of the cost savings will appeal to them, for sure - a “no brainer”. But vendor support that doesn’t cost an arm and a leg will be one of their arguments, I think. (I haven’t yet looked at Lucee tech support cost, so can’t really say.)
I have heard that Lucee is, quite often, ahead of ACF in many respects regarding functionality and robustness (ie, improvements to tags often appear in Lucee before ACF) which is something that I, as a coder, can appreciate.
If network security wasn’t so tight, here, I’d download Lucee now and install it on one of my development systems, just to see. Is the admin panel similar to ACF?
I am in the process of moving a large website to lucee from cf8. Not sure if it is because it was written on such an old version of cf or it is just the change to lucee, but there were quite a few problems. Biggest was PDFs. PDF creation is by using a plugin but apparently it doesn’t support multiple lines when trying to fill in a pdf form. If you use PDFs extensively, try that out first. Had to go through each form and break them down into single lines and programmatically figure out where each line goes. Not fun.
There seems to be some reserved words in Lucee that wasn’t in CF8 - hit a few of those.
I may be wrong - but when the email server gets clogged up and a cfmail fails, the file is written to a .tsk file in the web-inf/lucee / remote-client/ open (or closed) directory… but apparently you can’t just copy those to a queue directory like you can in cf. They are lost for good?
I haven’t optimized the server settings yet but right out of the box, everything seems much slower than on cold fusion 8.
On the other hand it is significantly cheaper -so probably worth the extra work.
Actually, they just replaced the last *nix server with a Windows server (not sure why). The Apache web server they don’t have a problem with, but they may not know that Apache is open source. Or Tomcat.
What is the difference between Express and the full-blown Lucee?
This is very good feedback from someone who recently went through the process. The only issue I have is with this statement:
I started switching from CF8 to Railo (Lucee’s predecessor) almost a decade ago. Railo was running so much more efficiently than CF8 (both memory and CPU), that I replaced 3 CF8 servers that were used for Load Balancing with a single Railo server which had still room to grow.
Sorry to hear about the issues you’ve been experiencing with the switch. I’d think that a lot of the issues are because CF8 is so old, now.
We don’t work with many CF generated PDFs. The most we do with PDFs is using Solr collections so that gigs and GIGS of PDF files can be index searchable. Something I should have asked @21Solutions about - does Lucee use Solr collections for keyword searching files and/or database tables??? How does it compare to ACF?
Unfortunately Lucee’s full text search, while exists, is not that great and hasn’t been updated much in recent years – don’t get me wrong – CF8’s was just as bad IMO. I’ve never tried newer versions of ACF beyond the basic comparisons of compatibility with Railo/Lucee, and did that on a need-to-do basis, so I can’t really tell more on that.
It also uses Lucene (not to be confused with Lucee) behind the scenes, just like SOLR, but provides a much easier interface. The best part is that if you use ElasticSearch externally (as opposed to the built-in search), then you have complete control over your search indices, queries, etc. So it’s definitely worth the refactoring IMO, even if you stay with ACF.
@WolfShade In regards to your original post, I’d like to point out that many open source projects get their bad reputation from just being a thing that some guy wrote and stuck on github with no support, etc. Lucee is open source which has a lot of benefits, but it is backed by a proper organization called the Lucee Association Switzerland (or LAS). The members of this organization include most of the major players in the CF space like Ortus Solutions (ColdBox), Blue River (Mura), Pixl8 (Preside CMS), Rasia (the original people behind Railo/Lucee), WebApper, etc. The member fees help pay for ongoing development, documentation, and support of the platform and the members themselves offer professional services such as paid bug fixes, paid features, and training for Lucee. This gives us the benefits of an open source project but with the support and constant activity of a commercial offering. Please ensure your higher ups realize this!
So in regards to white papers etc about switching to Lucee, I’m not sure if any exist but I can tell you that some very large companies such as NASA and ESRI are already using Lucee with great success. Specific benefits of Lucee include its modular OSGI architecture, extensible via modules, lightweight footprint, and advanced features such as the cache manager and better Cloud deployment via environment variable support and such.
Thank you for the additional pro-points, @bdw429s. I’ll be sure to include those in my presentation. Esp the bit about NASA and ESRI (I work for USG DoD - those might be huge bullet points.)
One thing that I’ve been meaning to ask: PDF/Excel/Word support.
I recently read a thread in Adobe forums in which someone had mentioned that Lucee does not have the full PDF, Excel, or Word support that ACF has. I haven’t, yet, Googled that. What can anyone tell me about the support or reported lack thereof??
BTW… I’ve been searching via Google for big name companies that use Lucee. Haven’t found one, yet. Does anyone know of a comprehensive list of companies that are using Lucee, either internally or for public-facing pages/apps?