> interpreter.. the explanation I received is that BD produces a tree
> structure of all tags in memory and on each call iterates this tree
> structure to call the classes and methods corresponding with each tag.
> Sounds like an interpreter to me, but I don't actually have a CS
> degree so
> perhaps I'm missing some distinction.��
>
You are correct in your explanation. The distinction is that those
classes and methods corresponding with each tag are already compiled
instead of having to be interpreted themselves. An interpreter in the
traditional sense would not use this hybrid approach.
> Also, being compiled doesn't necessarily mean faster either, 'cause
> most
> processing takes place in the code assiociated with the tags itself
> (written
> by MM and New Atlanta) as opposed to the code generated/interpreted
> by the
> CFML developer.��From what I saw the BD interpreter was extremely
> fast,
> although I've never run any empirical speed comparisons.
>
Without sharing actual benchmarks since we aren't allowed to per the
license, CFMX is faster than BD at executing a single page request most
of the time. CFMX may even be faster theoretically for many
simultaneous requests. However, BD seems to scale much better and is
able to serve more pages, faster when under heavy load.
> Of course, I don't see any way BD will ever have the Blackstone
> features
> already announced..notably the Flex integration (although I
> personally don't
> think this is a valuable feature), so we are likely to see
> framentation in
> the future and products can compete based on features and people will
> develop code that only runs on one "flavor" of CF, which is what I
> always
> saw as the problem with BD--it's always playing catch-up and any
> innovation
> it does just causes fragmentation.
>
What I have seen in Blackstone --cfdocument and rich forms-- could be
implemented in BD very quickly. As far as Flex integration, for the
small number of CFML developers who actually care about that, the
situation will be much the same way it is with Flash; integration will
happen using web services.
Of course, the future is hard to predict. I believe we as CFML
developers should look forward to the day when Macromedia implements
functionality in CF that is currently only found in BD. We will all
instantly know if we are doomed to have a fragmented language or if
Macromedia and New Atlanta can together serve their respective
customers without negative impact on the community.
-Matt
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
