For some reason I was under the impression that the ColdBox 3.0 system
was going to be refactored using component scripting instead of using
tags. I was really looking forward to it as I have begun refactoring
all of my handlers, events, and models using complete scripting, i.e.
public any function init(any controller) {
super.init(arguments.controller);
return this;
}
}
The only place I use tags now is in views. What's the hold up? My
application is looking more advanced than it's framework. Silly
rabbit, tags are for kids (and views).
Really, dude? I hate to be a naysayer, but not everyone wants to give
up the awesome tag-based language that is Coldfusion. Remember...if
you really, really, really like the script....you are MORE than
welcome to go pure Java. There's no tags to get in your way in
Java.
You know...as I write this...part of me says "relax, dude" (to
myself), but in the end, the statement: "Don't knock all the hard
work, hours and slave labor Luis has done on the framework and if you
don't like it, you don't have to use it, no one's forcing you to use
it" is what I'm really wanting to say. (And that's majorly toning it
down, believe me.)
I'm far more disappointed that you are knocking what you do or don't
get with (super free) Coldbox than you are with the specifics.
Really, dude? ....sigh.
More to the point, you want a script-based Coldbox Core? Awesome, it
is an open source project and is really easy to go fork the project on
Assembla. Go rewrite it!
And then who is responsible for bug fixes for the forked version? That would be a band aid for a symptom, not the problem. Tag based markup works on so many more platforms. For that reason, tagged-based markup is arguably more “advanced” (at least useful).
Presumeably, the people responsible would be whoever cares enough to
have a script-based version. That's generally how open source software
works. I agree that compatibility is more important than fanciness at
this point. Those who care enough to rework the project, however, are
welcome to if they feel that that is their best use of time.
My personal opinion is that I love scripting but cannot fully leverage it until further coldbox versions. 3.0.0 is the last version to support coldfusion 7. 3.1 will drop cf7 support and rely on cf8 and above features.
Once cf8 is no longer supported by Adobe then we drop cf8 and most likely rewrite core pieces to script as that is my favorite
Thanks Luis, your explaination is what I was looking for. So, the
underlying core is dependant on what Adobe currently supports for CF.
Makes perfect sense. And to the others, I'm not knocking CB in any
way, I love, love, love it! Aside from theology, Luis is a genius. It
is however correct to say "what does it matter what the framework core
is", as I can use all the scripting I desire on top. I'm sure that all
my hard work will fit right in when CB goes fully scripted. I'm also
not knocking tags either, it's really cool that we have a choice, some
like tags, others like code, uh, scripting I mean ;), joking. And I
resent the statement that I'm about what the code "looks" like, it was
meant to say that scripting is an evolutionary step foward, IMHO, with
CF and Adobe, i.e. "Advanced" as in advancing foward and adapting.
Cheers everyone and thanks for the input but Luis laid it to rest,
moving on..
