These last few days have been more exciting than anything CBS can offer. Can't
figure
out who's the snake and rat though. :)
I know neither Justin nor Jon, so I hope you can take my comments as being impartial.
But I sincerely think that the interests of both WebMacro and Turbine/WebMacro
user base will be best served if the two (Velocity & WebMacro) are united.
1. Is it possible for both project leaders to meet and agree on a NEW path that will
integrate the two projects with the agreement that the result will be a replacement
to
both the existing WebMacro code base and to Velocity as well? If it is indeed true,
what
Justin has been saying about Velocity essentially only having a great parser, then
not that much is lost by integrating the two. Velocity certainly got WebMacro
to affect it's rate of change :) So kudos to the name choice and its effect.
(I still like WebVelocity as a name choice or JWV).
2. Justin, concede all licensing issues to Jon. I'm sure your name will be
listed as a major contributor. Jon will insist on it; but you shouldn't.
3. Jon, I still don't understand how you can just rip out all of the WebMacro
stuff out of Turbine, without public input from the user base. I completely
realize the whole licensing thing was holding up turbine developers and you had
to do something, but given point #2, it seems a whole lot of work/time can be
saved by doing #1.
I have no clue to how much frustration was endured because you couldn't get
Justin to hand over the code to Turbine, but now he has. Jon, how you can be
so prolific given all the irons you have in the fire is beyond me, but
not having to re-invent WebMacro, will certainly save a ton of everyone's
time. It's not like WebMacro's code base is a bunch of crap.
4. Developers, if you have been hindered, by WebMacro dragging its feet,
I can understand your frustration, but it's over. Do you really want to waste
even more time, changing all your code and going with a project that's only
3 weeks old? Let's put the big picture first.
All the stuff over the last 36 hours is exactly why people are choosing JSP
over better technology. If Velocity does stop WebMacro development, you/i/us
will have a lot off pissed of managers/clients. But if we work together to actually
give them an improved tool it gives us more ammunition. I hate JSP. I had to
fight hard to show people there's a better way. Now I have to convince them to
switch to Velocity? ..ahhhhh I don't want to go back to the dark.
I know all the war metaphors can sound like a bunch of bs; but don't force a split.
split the winnings,
mike haberman
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
