I have been a CF dev since version 5 and it’s paid a lot of bills since then but, time to move on. I would never recommend CF for anyone due to the complete lack of a decent ecosystem and lack of direction from Adobe and Lucee. Once one looks at .net core C# and F# you can’t make any good argument to continue with CF. Using C or F sharp I can develop native apps and high performance web API’s, event sourcing, testing platforms from Canopy, Spec Flow, NUnit, Xunit etc......
I mean my gosh Adobe is still actively spending resources with keeping tags alive! They now add covariant into the language, why? They should have open-sourced 10 years ago and maybe we would have something.
Just have a look at the SAFE stack, Fable or one of the million other options and huge community dedicated to open source in .net core. VS Code is a great example of what can happen or the F# compiler that is maintained outside of Microsoft as open source.
Coldfusion software engineer - yes, Coldfusion. When I'm not debating the finer points of software development, I can be found pedaling furiously along a winding country road.
It's pretty obvious Adobe has done a lackluster job in determining a direction for their implementation, but decrying ACF as closed-source is a poor argument when Lucee is both open source and far better.
The SAFE stack looks pretty interesting. Fable looks kinda stupid in my opinion - if you want a JS app, write JS!
I'm not sure why I have to take a look at a million other options when CF works really well for me.
Referencing other projects as "kinda stupid" unfortunately, is the attitude I have encountered among the vast majority of CF devs I have worked with or met over the years and is the main thing that has me going down another path. If you think Fable is "kinda stupid" you also need to include Clojurescript, TypeScript, Elm, Dart, Flutter, Fabulous, Rust, etc.... Fable simply allows F# devs to maintain their style of functional programming and quite frankly I am not at all wild with the direction of JS anyways. We are getting very close to having WebAssembly becoming a standard and you should ask yourself where is Lucee or Adobe providing this ability to use CF, and then look at what is going on with .net Core, Go, Clojure, etc...
Coldfusion software engineer - yes, Coldfusion. When I'm not debating the finer points of software development, I can be found pedaling furiously along a winding country road.
Coldfusion software engineer - yes, Coldfusion. When I'm not debating the finer points of software development, I can be found pedaling furiously along a winding country road.
My apologies again @Robb. I didn't mean to get so sarcastic. If you think CF is falling behind, that's ok. I wouldn't mind a few constructive tips on how to improve the language or ecosystem, and we can stop badgering each other. :)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I have been a CF dev since version 5 and it’s paid a lot of bills since then but, time to move on. I would never recommend CF for anyone due to the complete lack of a decent ecosystem and lack of direction from Adobe and Lucee. Once one looks at .net core C# and F# you can’t make any good argument to continue with CF. Using C or F sharp I can develop native apps and high performance web API’s, event sourcing, testing platforms from Canopy, Spec Flow, NUnit, Xunit etc......
I mean my gosh Adobe is still actively spending resources with keeping tags alive! They now add covariant into the language, why? They should have open-sourced 10 years ago and maybe we would have something.
Just have a look at the SAFE stack, Fable or one of the million other options and huge community dedicated to open source in .net core. VS Code is a great example of what can happen or the F# compiler that is maintained outside of Microsoft as open source.
The landscape has changed and CF is being buried.
It's pretty obvious Adobe has done a lackluster job in determining a direction for their implementation, but decrying ACF as closed-source is a poor argument when Lucee is both open source and far better.
The SAFE stack looks pretty interesting. Fable looks kinda stupid in my opinion - if you want a JS app, write JS!
I'm not sure why I have to take a look at a million other options when CF works really well for me.
Referencing other projects as "kinda stupid" unfortunately, is the attitude I have encountered among the vast majority of CF devs I have worked with or met over the years and is the main thing that has me going down another path. If you think Fable is "kinda stupid" you also need to include Clojurescript, TypeScript, Elm, Dart, Flutter, Fabulous, Rust, etc.... Fable simply allows F# devs to maintain their style of functional programming and quite frankly I am not at all wild with the direction of JS anyways. We are getting very close to having WebAssembly becoming a standard and you should ask yourself where is Lucee or Adobe providing this ability to use CF, and then look at what is going on with .net Core, Go, Clojure, etc...
My apologies, I actually thought for a minute I was allowed to have an opinion.
You can write JS in Java as well through GraalVM, Nashorn, Rhino, or several other libraries but I still fail to see the point.
My apologies again @Robb. I didn't mean to get so sarcastic. If you think CF is falling behind, that's ok. I wouldn't mind a few constructive tips on how to improve the language or ecosystem, and we can stop badgering each other. :)