CFScript is a band-aid solution, it is not possible to use every CFML tag from CFScript, the implementing server has to provide a function, there is no documented way of adding top level CFScript functions, when one wants to wrap a tag in a function - good luck without having to write temporary files...
These 2 engines are not fully compatible with the official closed-source version. For example, BlueDragon handling of importing / creating instances of objects highly deviates from Adobe CF. Lucee has a whole page dedicated to unsupported tags: docs.lucee.org/reference/unsupport... and their own tags: docs.lucee.org/reference/additiona....
It's pretty simple. Don't use Adobe CF, Lucee Server is the engine that has moved CFML forward and along with it the community. Die-hard proponents of Adobe CF are companies that think if you pay for something it means it's better.
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.
You need to find better sources.
You're killing me dude. Your point one was correct 5 years ago. Your second point is not an issue if you know what you are doing.
You seem to have a short fuse. Even COBOL is great, if you know what you're doing.
It's pretty simple. Don't use Adobe CF, Lucee Server is the engine that has moved CFML forward and along with it the community. Die-hard proponents of Adobe CF are companies that think if you pay for something it means it's better.