On Fri, 2010-04-30 at 07:57 +0200, Kevin Kofler wrote:
But of course the underlying true issue is that Mozilla is refusing
to
guarantee backwards compatibility for the interfaces pretty much all
existing apps used and in several cases still use, instead trying to force
everyone to port to their new public API. I can't judge whether the original
interfaces were so poorly designed they really can't be kept compatible
(which reflects poorly on Mozilla) or whether they're just adding a useless
wrapper because they refuse to stay compatible (which reflects even more
poorly on them).
With the caveat that I'm not really familiar with the situation, I think
that assessment is unfair. If Mozilla feels the private interfaces are
suboptimal and wants to adjust the design before committing to long-term
stability, I think that's a reasonable decision. Let he who gets
everything right the first time throw the first stone.
--
Matt