Hi all
I've been reading the current posts about Freemaker and I think it is
time to share my point of view.
I believe Turbine should be "tool-agnostic". What do I mean? Turbine
should (and I think, it does most of the time) provide a framework which
should be able to work with whichever tool I decide to use. An example for
this: OR mapping tools. I know most people around Turbine like Torque.
Still, I don't. I may change my opinion later, but so far, I prefer other
tools like Hibernator. So I think Turbine should provide a trully
"tool-agnostic" framework where I could use Hibernator without any strings
attached to Torque.
Is this the current state of Turbine? I don't think so. We still have
strong dependencies to specific tools (being Torque and Velocity the most
obvious ones). It is like Microsoft telling me that it is impossible to
create a good Operating System without having Internet Explorer embeded.
What about Velocity? I like Velocity. We have a commercial project here
written with extensive use of Velocity. Could Velocity be better? Sure it
could. Is it getting better? Not even people in Velocity dev team agree on
that. So should Turbine decide to drop other Templating Engine support? I
really don't think so.
What could be done to become a trully "tool-agnostic" Framework? I like
the way Eclipse project has managed to stay completely agnostic. They focus
on having a great IDE platform and publish lots of documentation on how to
extend it. The community does the rest. And so far, there are hundreds of
pluggins for Eclipse.
So, I know FM people may haven't tell things the right way, but I think
they deserve a place (like anyone else) around Turbine. Let's make sure they
have it... Let's make sure we all have it...
Rodrigo
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
