+1 to all of this - I support all of your points and currently it's what's kept me on 1.2.2.
I can usually defend upgrade teething problems with my users; not this time sadly, especially when I'd be looking at a bill for £1499 to do it. On 13 Nov 2011, at 07:24, raj <[email protected]> wrote: > Fine. If the second digit in your version number is to be understood > as a protocol incompatible change, this is not normally the case and > it needs to be clearly stated. It currently is not. What's happening > currently, is that people are thinking that version 1.3 is simply "the > next update" and that they can download it without issues. When they > find that version 1.3 doesn't talk to version 1.2 programs, they're > getting upset. Why? Because that's unexpected. I simply think it > needs to be clear to people that Growl 1.3 is not protocol compatible > with Growl 1.2. Normally, a major version number change conveys > this. If you don't want a major version number change, that's fine, > but then it needs to be made clear in some other way. > > (I'll go farther to point out one simple example. Go to "growl.info" > and look at the reasons under "Why use Growl?" The first one says, > "When you start up a Growl-enabled application, it will just work." > This is clearly and demonstrably wrong. Skype is a growl enabled > application. It doesn't work with Growl 1.3 currently. We all > understand why. That's not the point. The point is dealing with > people's expectations. As a programmer, your programs [usually] > interact with people. That entails a responsibility to deal with > people's expectations. I've been in the industry for over 30 years > and I've learned that handling people's expectations is the hardest > part of the work.) > > /raj > > > > On Nov 12, 1:03 pm, Chris Forsythe <[email protected]> wrote: >> We didn't name it 2.0 because it's not where we want Growl to be when called >> 2.0. There's UI work we're still considering. 1.4 will make translating >> Growl much simpler for starters, and things like that. There's lots of UI >> and backend work overall that is coming down the road. :) >> >> -- >> Chris Forsythe >> >> >> >> >> >> >> >> On Friday, November 11, 2011 at 1:24 AM, raj wrote: >>> Thanks for the clarification. I was coming to that same conclusion, >>> but it's good to hear something definitive. This is, of course, only >>> one of many reasons why Growl 1.3 should have been named Growl 2.0. : >>> ( >> >>> Thanks for the clear and concise response. >> >>> /raj >> >>> On Nov 10, 11:05 pm, Christopher Forsythe <[email protected] >>> (http://growl.info)> wrote: >>>> growlnotify for 1.2 can't talk to 1.3, and vice versa. >> >>>> You could use a gntp library (there's plenty, pick a langauge) to send a >>>> notification to Growl >>>> 1.3.http://growl.info/documentation/developer/bindings.phphasmore >>>> information >>>> on that. >> >>>> Chris >> >>>> On Wed, Nov 9, 2011 at 7:44 PM, raj <[email protected] >>>> (http://mischievous.us)> wrote: >>>>> I have an older Mac which can't run Growl 1.3.1 but has an >>>>> installation of Growl 1.2. Can the "growlnotify" associated with >>>>> Growl 1.2 actually send messages to a Growl 1.3 system? When I try >>>>> it, I get: >> >>>>> 2011-11-09 17:43:35.905 growlnotify[44968:903] Exception: >>>>> NSPortTimeoutException >>>>> Segmentation fault >> >>>>> If the 1.2 version of growlnotify is capable of sending message which >>>>> can be correctly received by Growl 1.3, I'd like instructions on how >>>>> to do it. >> >>>>> Thanks. >> >>>>> /raj >> >>>>> -- >>>>> 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] >>>>> (mailto:[email protected]). >>>>> To unsubscribe from this group, send email to >>>>> [email protected] >>>>> (mailto:[email protected]). >>>>> For more options, visit this group at >>>>> http://groups.google.com/group/growldiscuss?hl=en. >> >>> -- >>> 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] >>> (mailto:[email protected]). >>> To unsubscribe from this group, send email to >>> [email protected] >>> (mailto:[email protected]). >>> For more options, visit this group >>> athttp://groups.google.com/group/growldiscuss?hl=en. > > -- > 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. > -- 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.
