On Oct 7, 2011, at 07:35:59, Perry E. Metzger wrote: > The developers did not test the upgrade mechanism well …
It isn't possible to test MAS upgrading without releasing through the MAS. > … and altered the interface between growl and applications … This is untrue. The interface that Growl provided to applications from 1.1 or so onward is still supported. > (claiming it is the fault of app developers for not having all upgraded to > the new and unreleased framework in advance), This is untrue. App developers did not keep up to date with RELEASED frameworks. Version 1.2.2, the most recent release, when used correctly, works. > and failed to release any of the auxiliary software like the itunes growl > addon at the same time. They are separate products which the Growl developers announced previously they will release separately and not at the same time. > The code is also buggy and crashes for many people. I've only seen one crash reported for Growl 1.3 (the queuing-display crash). > They have also (apparently) taken the code closed source (at least for now) > so no one can try to fix the problems on their own and release fixed versions > outside of the Growl developers themselves. Not for that reason, no. It was because the team (which included me at the time) worried about export restrictions on encryption code. Now, there's no strong encryption in the code anymore (I stripped it out). I don't know why the current developers haven't reopened it; it's up to them. They may simply have not had time; they've certainly had plenty of other work to do on Growl. > They have generally posted messages here [saying …] why are we complaining. No Growl developer has said that. -- You received this message because you are subscribed to the Google Groups "Growl Discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/growldiscuss?hl=en.
