Thanks for the response Alan W;

I'm not concerned about CFML's current coolness. People still pay me to use it, that's cool enough for me.
I don't care about a CFML standard (if there ever really was one), as long as I can get it to do what I need.

It's reassuring to know you guys are still dedicated to the OpenBD engine. But we're not privy to all your decisions and discussions with Andy regarding release cycles, so we don't know what to think after some time goes by and the site goes unchanged. Personally I think it's a good idea to put down a marker once a year or so, package everything up, zip a new desktop edition, then update the web site about it.
OR
I suppose another idea would be a little cf admin script to automate the update process (download newer jars, put them here)... but that's a whole new discussion.

Another factor that was contributing to my fears is this email group. While I think Mats and Marcus and I attempt to field as many threads as we feel qualified to - there seems to be an increasing number of questions that fall through the cracks; some of which are possibly people trying out OpenBD for the first time. We don't have contributions from Matt W or Peter F or Jordan M to help us address them any longer.

You guys may be too busy to answer every one (which is a good thing for you), but we just don't know that. So instead, we get nervous about support in general. Well, at least I do...

Thanks again. I appreciate all you guys do.
Al

On 1/31/2014 11:14 AM, Alan Williamson wrote:

On 31/01/2014 12:39, Alan Holden wrote:
Done. My only real concern about CFML in general, is the ongoing support for OpenBD in particular.

Do not worry on that front.  OpenBD is continually updated, we just don't formally release versions to be honest with you, and it is something we've been toying with in terms of a continual build/release cycle.    By the time we are committing code to the base, its been thoroughly tested, and rarely have we had to back out a change.

So we may just keep the nightly builds and keep some previously changes.   It is something Andy and I are talking about.

But we use OpenBD very aggressively with our projects and are continually looking at ways to improve the engine.    It is no secret that I personally have no interest to be feature compatible with any other alternatives;  if people want a feature, then ask and we'll consider it, or we'll accept code submissions.   But the days of an official CFML standard are long gone.

When i describe OpenBD to others I merely say its CFML based in its origins, but then don't discuss the CFML language at all.   It's just a powerful web scripting language as far as i am concerned.

CFML as a language IMHO has its day of being the cool-kid-on-the-block.
--
--
online documentation: http://openbd.org/manual/
http://groups.google.com/group/openbd?hl=en
 
---
You received this message because you are subscribed to the Google Groups "Open BlueDragon" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

--
--
online documentation: http://openbd.org/manual/
http://groups.google.com/group/openbd?hl=en
 
---
You received this message because you are subscribed to the Google Groups "Open BlueDragon" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to