3 ms·

You wouldn't build apps with this. It's essentially a modern implementation of a ColdFusion engine. CFML is quite arguably an abandoned language and should neve

You wouldn't build apps with this. It's essentially a modern implementation of a ColdFusion engine. CFML is quite arguably an abandoned language and should never be used in new projects. The only meaningful use case I see in Lucee is to be able to run and maintain legacy CF applications in an environment that is still supported without rewriting them for a more modern and capable language/runtime. It would be best utilised for putting legacy applications on life support, not for creating the next big thing.

rmason 8y ago
I've got a lot of friends building new apps using it. I'm using it for the REST back end of my new startup. There's a strong vibrant community on Slack. It may not be as popular as other languages but it has two advantages: 1. Rapid application development 2. A glue that ties other enterprise apps together I got into a fight on Twitter over using CFML for new projects with a rather prominent fellow in the coding world. The year was 2008 and a lot of apps have been written in it since then;<).
abraham_lincoln 8y ago
I disagree. If you want legacy support, simply use the older Adobe provided Linux CF engines. Look at the Coldbox framework and you will be pleasantly surprised at the implemented best practices and ease-of-use, all running in Lucee.
sjwright 8y ago
> You wouldn't build apps with this. Why not? The environment is feature rich, runtime performance is fantastic, developer productivity is exceptional, and integration is compelling because it runs in the JVM. Yes, the JVM. So even if Lucee doesn't do what you need, you can natively call upon countless Java features like javax.script or javax.crypto, or third-party Java libs like JSoup or Lucene with just a couple extra lines of code. And yes, like any language, it doesn't stop you from writing incompetent and stupid shit. The one big knock against the ColdFusion-inherited language is that the templating syntax is often overused for writing code, when it also has a great C/Java/JS-style scripting syntax.

rmason 8y ago

I've got a lot of friends building new apps using it. I'm using it for the REST back end of my new startup. There's a strong vibrant community on Slack. It may not be as popular as other languages but it has two advantages: 1. Rapid application development 2. A glue that ties other enterprise apps together I got into a fight on Twitter over using CFML for new projects with a rather prominent fellow in the coding world. The year was 2008 and a lot of apps have been written in it since then;<).

abraham_lincoln 8y ago

I disagree. If you want legacy support, simply use the older Adobe provided Linux CF engines. Look at the Coldbox framework and you will be pleasantly surprised at the implemented best practices and ease-of-use, all running in Lucee.

sjwright 8y ago

> You wouldn't build apps with this. Why not? The environment is feature rich, runtime performance is fantastic, developer productivity is exceptional, and integration is compelling because it runs in the JVM. Yes, the JVM. So even if Lucee doesn't do what you need, you can natively call upon countless Java features like javax.script or javax.crypto, or third-party Java libs like JSoup or Lucene with just a couple extra lines of code. And yes, like any language, it doesn't stop you from writing incompetent and stupid shit. The one big knock against the ColdFusion-inherited language is that the templating syntax is often overused for writing code, when it also has a great C/Java/JS-style scripting syntax.