You obviously didn't read the rest of my email where I explained our plan. I 
understand you don't like the path we took, and I honestly am sorry that you 
feel this way about it. 

But I wouldn't change it. Bottom line is that this change was necessary. Nobody 
is forcing you to use 1.3, and feel free to get a refund. But this is a 
distraction from us making 1.3 better for the very issue you are trying to tell 
us to apologize for.

This is the end of this argument. Growl 1.3 will not be pulled, and I'm not 
going to apologize about applications not keeping up 6 years and 4 years and 2 
years out with code that they ship. I'm not going to apologize for applications 
which are not using our recommendations. You dislike this, I understand that, 
but this is how it is. As I explained in my previous email, here is our plan:

1) Growl 1.3 is not going to be pulled from the app store.

2) Growl SDK 1.3 will include a framework that will return YES for every call 
to isInstalled. Which will resolve the problem for those who can't get Skype 
working, for instance.

3) Once the 1.3 SDK is out, we're going to work on making the Growl Version 
Detective provide a way to click a button to replace the framework using the 
1.3 framework. So that all you do is load up GVD, and then click a button if 
the framework is older than 1.3 to replace it, or something like that.

I'm sorry you feel this way about the 1.3 release, and hopefully future 
releases will be better for users, since applications will be addressing the 
problem that their incorrect use of the api caused. However, that doesn't 
change the fact that for a lot of people 1.3 works fine, and if they have to 
perform one framework replacement it's not the end of the world and in fact 
it's pretty simple to do. You are making a big deal over something that within 
a month or two will not be a big deal at all based on the items I mentioned in 
my previous email, reiterated in this email.

I would expect that this should be the last email on this thread, since there 
isn't anything left to discuss on this issue. 

-- 
Chris Forsythe


On Sunday, October 9, 2011 at 2:17 PM, Perry E. Metzger wrote:

> On Sat, 8 Oct 2011 23:55:40 -0500 Chris Forsythe <[email protected] 
> (mailto:[email protected])>
> wrote:
> > You can argue about this until you are blue in the face, and we can
> > argue back. But in reality if an application is not working, out of
> > the box, with Growl 1.3 then they did something which needs to be
> > corrected.
> 
> That might be plausible if it wasn't the overwhelming majority of
> apps people care about, or if you were not charging people for the
> privilege of using a new version of Growl. However, most things are
> broken, not just a few odd app developers, and the majority of your
> users are indeed broken and yet paid money to get into the state
> where they lost functionality they had before.
> 
> You are being obstinate in the face of a clearly articulated
> anger on the part of your user community.
> 
> You can explain to us until you are blue in the face that it isn't
> your fault that everyone had a working 1.2.2 installed and now that
> they have no working application, that it is the fault of all those
> app developers for not updating their stuff, that it is the fault of
> Apple for making it hard for you to test your broken installer, and
> so forth, but in the end we paid money for a product upgrade that
> broke our functionality.
> 
> Were I in your position, I'd admit that it was my fault, withdraw the
> product until it was fixed, and apologize profusely.
> 
> However, that would require the strength of character to admit that
> you're wrong in public, which many people seem to be unable to do.
> 
> Anyway, I'm sure it is easier in the short run to keep on telling us
> how it is everyone's fault but yours, but all you're doing is
> destroying good will in the name of demonstrating that everyone else
> is wrong and you're right. Very soon you will have destroyed years of
> goodwill in order to avoid admitting that you made a mistake.
> 
> Oh, and by the way: telling people to hand update frameworks, run bits
> of applescript, etc., doesn't cut much ice with your users either.
> 
> Perry
> -- 
> Perry E. Metzger [email protected] (mailto:[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.

Reply via email to