On Fri, 30 Apr 2010 15:20:49 -0300, Josh Canfield <[email protected]>
wrote:
A change regarding how translators are contributed wouldn't
be an issue, I guess. Few lines of code would need to be changed.
While I agree that it is a small issue to fix for most developers,
it's still a bullet point on the "tapestry versions aren't backward
compatible" list. If you're on a project with any tapestry doubters it
will add to the difficulty in getting more projects done with
Tapestry.
I agree, but that's a very different scale. Tapestry 5 was 100%
incompatible with T4, and we're talking about a small change. As Howard
said, there are situations that keeping perfect backward compatibility
while still improving the framework is impossible.
By the way, in the mailing list, there were people complaining that T5
wasn't compatible with T4 and other people complaining that T5 will be
always backward compatible, so it won't evolve and then it will die
(http://old.nabble.com/Tapestry-6%3A-Famous-last-words--to24225398s302.html#a24230166),
and that wasn't a troll. Perfect backward compatibility isn't a good
trade-off, IMHO.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
