On Fri, 7 Oct 2011 12:10:11 -0700 Peter Hosey <[email protected]> wrote: > On Oct 7, 2011, at 11:20:16, Perry E. Metzger wrote: > >>> … 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. > > > > Then why don't old apps continue to work with growl without > > alteration? > > Some of them do. > > The ones that don't use old frameworks that include a bogus check > for a Growl prefpane (1.3 isn't a prefpane).
So the presence of a prefpane was, in effect, a portion of the API. > > The answer is that you altered the interface … > > That is incorrect. It is evident that it is correct -- the old programs wouldn't be broken otherwise. Even a few hours of testing would have revealed that 1.3 didn't work with a wide variety of existing programs. You had a number of choices here -- releasing a 1.2.x series that still did a prefpane while waiting for people to update more applications, waiting until app developers no longer were mostly using the old system, etc. You didn't do that. You also had and still have the choice of withdrawing 1.3 from the app store after discovering it was broken, etc. That hasn't been done, either. > > and are asking all your developers to update their code. > > That *is* correct. App developers are using old versions of the > Growl framework that have bugs, including this one that is critical. > > > Unless you know that (almost) everyone has upgraded, you don't > > change an interface... > > And the Growl project did not change the old interface. Pardon me, but if that were true, old apps would still work. > >>> 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. > > > > Thus breaking your users. > > How so? The latest version (1.2.2) of GrowlTunes and > HardwareGrowler still work. HardwareGrowler is totally broken now actually, and I've been unable to get the old GrowlTunes to work. Have you tried them? Have you looked at people complaining? growlnotify also is broken and I depended on it heavily. > >>> 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). > > > > I've seen a lot of crash reports in the last few days, and you > > haven't answered most of them. > > I'm going to withdraw my statement because it's misleading on a > couple of points: > > 1. I'm not a Growl developer anymore. > 2. The Growl developers can see all Growl 1.3 crashes (in iTunes > Connect); I can only see crash logs posted on the list. > > The developers know what crashes Growl 1.3 has. > > I'm answering most of the emails to let the actual developers do > actual bug-fixing work. The first thing they should do is withdraw 1.3 until a working version is available -- this is now a paid app, and people paying money have an expectation that what they paid for will work. The second thing they could do, if they wanted things to be fixed quickly, is make the source code available again so other people can help them with the bug fixing. -- Perry E. Metzger [email protected] -- 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.
