The State of Lucee

language
22

Just a few ideas here.

I think Lucee and CFML are mature. Thus the need I see is less on more syntax and language enhancements but more in making the eco-system easier to use, deploy and manage.

This to me entails, looking at enhancing the tooling and supporting people along their whole dev life-cycle: What are the tasks that eat a lot dev time? Which environments do devs use? Where do their customer want to deploy and manage?

The attractiveness of node and .net is that there are many tools that spell out the whole ecosystem, i.e. devs have a cookbook. This is where I would also place the box language efforts.

In other words, I am still hoping for easier “Cloud Native Development” with Lucee without workarounds and manual steps.

For example, Lucee could have a command line tool like node or .net and make it easier to create frameworks and projects that deploy with one line. The early versions of the “serverless framework” were a good example in my opinion.

How attractive would it be to have a tool that allows you to develop locally and push things with one line for the world to see.
e.g.
lucee push staging --AWS
Make same starter frameworks and templates available for common use cases, e.g. RESTAPI, GraphQL, TODO, TaskRunner, Lambda, etc.
lucee create ProjectName --RESTAPITemplate --dev --AWS

Cheers,
Bilal

4 Likes
23

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 :slight_smile:

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 for someone.

Cheers

2 Likes
24

I do that using git. I wrote a bash script so I simply run gp (short for git push) from the repo’s folder. I even have database changes scripted via .sql files which are executed via post-update hook. After successful push, my script plays a short video clip of one of my favorite scenes from Silicon Valley: “He pushed another commit! What the #^&$!” Been using my gp script for some years and still not tired of that cherry on top, though sometimes I do mute before deploying. :rofl:

3 Likes
25

Maybe have a banner in the admin that you can use to communicate with admins? Put a ‘Send us your success story’ there?

Subscribe to mailing list form in admin panel? (put form directly in there, make it EASY… have some checkboxes : major versions, news, new features - have a few different types of lists so people can get occasional or all the emails. …rather than Mailing list which is pointing to the YEARS old lucee google group #lol @Zackster - need to get that link updated in admin panel dashboard (bottom) bro! (and add the slack channel link Redirecting… | Slack)

Maybe just move that whole section at bottom with links to pro services / support into a ‘Get Help’ under overview in admin panel. Make it MORE visible and accessible to get to the dev.lucee.org and slack links

Commandbox works great for lucee? why would you consider writing another one?

26

That comment was in reference to what Bilal said…

Yes, CommandBox is great, no question… althought it has a slow startup :wink:

But if someone wanted to build a Lucee centric CLI that could help save time, why not? There is always room for to make things better. In fact Mark Drew is a great example of doing just that.

But to your point, there probably isn’t much motivation since CommandBox works great for Lucee as you said.

1 Like
27

for things like a CLI, please start a new thread to discuss, otherwise, we are dealing with wading thru a 400k utils.cfc file!

You can always just paste a link into the new post pointing to an older post, the forum will cross reference it automatically

1 Like