On Thu, Aug 6, 2009 at 11:56 AM, Kevin Kofler<kevin.kofler(a)chello.at> wrote:
Christopher Aillon wrote:
> Sure, you can blame Gecko for having it's unstable ABI be, well,
> unstable. But blame also goes to the apps for not using the stable ABI.
Why does Mozilla expect apps to use an ABI:
* which didn't exist when the apps were written and
* which they aren't even using for their own apps?
Everyone complains about M$ using internal W32 APIs in IE,
who does that?
why does Mozilla
do the same with internal xulrunner APIs? If you think everyone should use
the stable ABI, why is Firefox not using it?
I don't see whats wrong with providing a an ABI that you can/want to
support (i.e no ABI breaks for minor updates) and one for your
internal use (i.e you know when it breaks and therefore fix your own
app).