Native Lucee CLI (comparable to Python)

[kenricashe]

@Zackster suggested a split from @noursecode’s topic:

The State of Lucee

Great ideas Bilal, no doubt. My initial question was to the core team, just to get a gauge on where things are. As an open source community, if not the core team, your suggestions could be solved by volunteer contributors. I’m thinking the Lucee core team might be a little booked at the moment You do have to hand it to Brad Wood and Ortus, although it is not Lucee centric, CommandBox is commendable. But could a CLI be built for Lucee only? Sure, it’s certainly an opportunity …

I’m curious how we might benefit from native Lucee CLI capability instead of using CommandBox.

My first thought is improved performance.

And I personally welcome Lucee decoupling from Ortus, especially since they are now more competitors than supporters.

[dawesi]

commandbox is powered by lucee right now from what I understand??

I’ve not seen anything that says Ortus are not supporters anymore of Lucee as an engine.

are you suggesting a fork of commandbox? right now for what benefit?

[kenricashe]

@dawesi Not sure what you mean re: “powered by Lucee”, as Commandbox is a standalone Ortus product. And supporting Lucee “as an engine” doesn’t mean they wouldn’t love for all Lucee devs to migrate to BoxLang. At the very least it’s obvious where the vast majority of their resources are allocated now.

I do not use any Ortus products including “Project Gideon” and never will. Native Lucee CLI would be ideal. Ironically in a recent thread you said that competition is good for developers! And this is an opportunity for Lucee to do it better. I already stated the benefit (better performance) and it could put Lucee in more of a position to be comparable with Python for example.

I’m not saying it’s a priority. Just posted this in a new thread since that was suggested.

[dawesi]

I’m coming around the idea. I use tesbox and commandbox, but looking at writing my own testing framework also as I need some more flexibility, but love testbox and what it’s done for our community.

There is some things I’d like to see with forgebox that ortus just aren’t motivated to do, like moving from a single category to tags. Working toward releasing a teamcfml repo with tags lookup support, and with support for the lucee extensions library (currently called ‘applications’, please, please change this in v7 @Zackster, @cfmitrah )… it would be so less confusing.