we know already know. Said
learning curve removes any benefit, leaving us back with "what I already use is
the best solution for me".
>>>> [EMAIL PROTECTED] 6/6/2007 9:36 AM >>>
>Randy Will wrote:
> > What all this comes down to is that "ease of use"
What I see as an optimal model for RR isn't far at all from what we have now.
I believe that the engine should stay closed as the core team seems pretty well
able to handle that. I think the plugin structure and SDK needs to be
developed into more of a FOSS community (by this, I mean that Rev
The issue with this is that "easier to use" is a very subjective area.
Generally, in the tech sector, "easier to use" actually means "easier to use
for someone who has been entrenched in the MS Windows world for the last 10
years." This is how MS gets all of their Cost of Ownership studies to
I have to agree that Open Source is currently a fad in the tech market. All of
the monthly rags are really starting to get into it. On the other hand, you
have to give some value to the movement away from a completely closed
development model.
Disclaimer: I am a cross-platform accessible so
