[Adium-devl] Synchronizing with libpurple

[bgannin]

That's the 'goal' but it's not always the result and with the  
criticality of libpurple it's not something I'd like to see exposed  
to the general public for fiddling with as an 'option'.

To me it's not unlike how APIs/frameworks in Mac OS X are  
fundamentally 'stable' but between any given version internals may  
change (that may result in unexpected consequences for consuming  
apps), and between major versions APIs may deprecate or mutate due to  
requirements (I sound dramatic, but I realize this is an extremely  
minor possibility). It's something both sides of the API contract are  
aware of - OS/API vendors provide early access, consumers of the API  
verify expected behavior or report issues so that by the time the  
general public (who is not actually a part of said contract) is  
involved, there hopefully won't be any unforeseen regressions (with a  
proper QA cycle.)

- brian 'bgannin' ganninger


On May 29, 2007, at 11:49 PM, Ofri Wolfus wrote:

> I'm not saying we should do it either, but isn't one of the goals  
> for frameworks is to provide backwards compatibility (I'm speaking  
> about that version/current directory structure)?
>
> It seems to me that updating only the framework is the same as  
> updating the entire app. In both cases the app would have to be  
> restarted, so the only benefit of updating only the framework is a  
> smaller download.
>
> - Ofri
>
> - - - - - - - - - - - - - - - - - - -
> http://www.dpompa.com
> - - - - - - - - - - - - - - - - - - -
>
>
> On 29/05/2007, at 23:58, bgannin wrote:
>
>> Just because it may be a separate framework does not imply API or
>> feature parity. With any given update underlying parts may change in
>> a way that exposes a new issue in previously fine code, creates an
>> entirely new issue, or much more. This may not be the case, but its
>> certainly a possibility. Moral of the story - being a framework (and
>> if I recall correctly, we actually build the framework manually, not
>> just 'get' it from Pidgin) doesn't mean you can assume a 1:1
>> relationship at any time allowing replacement. Updating a core
>> component requires a proper QA cycle to vet any breakage that may
>> occur and shouldn't be foisted on the user to do so.
>
> _______________________________________________
> Adium-devl mailing list
> Adium-devl at adiumx.com
> http://adiumx.com/mailman/listinfo/adium-devl_adiumx.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://adium.im/pipermail/devel_adium.im/attachments/20070530/6e773781/attachment-0001.html>