Re: [Prototype-core] Re: Native JSON breakage

2009-12-02 Thread David Kaufman
Hi Bob,

I'm sure there are a few things Google could do:

Bob Aman boba...@google.com wrote:
 [...] my issue here is that while we're waiting
 for a newer version of Prototype, more sites are deploying the current
 version, and every time they do, that's one more site that's now
 incompatible with some of our APIs.  Plus, there's not exactly an
 auto-update feature for JavaScript libraries.  

Sure there is (and Google provides it):

   Prototype hosted on Google's servers
   http://tinyurl.com/google-hosted-prototype

I guess the left hand doesn't always know what the right hand is doing 
in an organization as large as Google :-)

  For every user that contacts our support team (and hopefully, gets
 correctly diagnosed and given a fix) there are ten more that give up
 before even talking to support.  Of those ten users, most will assume
 the problem is Google's fault, because the visible breakage happens
 in our code even though the bug is Prototype's.

Why not enhance (and future-proof!) the Google Friend Connect code, 
right where it fails, to simply check the (by now, already loaded) 
Prototype.Version number, and if it's the version with the bug, throw an 
error which says something helpful like:

   Detected Prototype 1.6.1: This version of Prototype is not
   compatible with Google Friend Connect.  To resolve this issue:

   A. Upgrade to the a newer release of Prototype

   B. Run out patched version of Prototype 1.6 hosted at
  http://ajax.googleapis.com/prototype/1.6-patched/prototype.js

   C. See our http://support.url for more info, and other ways to
  work-around the bug, and resolve this issue.

 I'm happy to contribute patches or do
 whatever you guys need to make this fix happen.

Mailing Tobie and Andrew bags of cash, or giving them great-paying 
no-show jobs at Google probably couldn't hurt either :-)

-dave

-- 
You received this message because you are subscribed to the Google Groups 
Prototype: Core group.
To post to this group, send email to prototype-core@googlegroups.com
To unsubscribe from this group, send email to 
prototype-core-unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/prototype-core?hl=en


Re: [Prototype-core] Re: Native JSON breakage

2009-12-02 Thread Tom Gregory

On Dec 2, 2009, at 8:36 AM, Richard Quadling wrote:

 2009/12/2 David Kaufman da...@gigawatt.com:
 
 Mailing Tobie and Andrew bags of cash, or giving them great-paying
 no-show jobs at Google probably couldn't hurt either :-)
 
 I wouldn't mind one of those great-paying jobs. I'll turn up! I'll
 even wear the t-shirt.
 
 -- 
 -
 Richard Quadling

I'm sorry, but by volunteering to show up for a no-show job, you've violated 
the terms of employment, and are thus no-longer eligible for this position.

I, on the other hand, promise to not show up.

=)


TAG

-- 
You received this message because you are subscribed to the Google Groups 
Prototype: Core group.
To post to this group, send email to prototype-core@googlegroups.com
To unsubscribe from this group, send email to 
prototype-core-unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/prototype-core?hl=en


Re: [Prototype-core] Re: Native JSON breakage

2009-12-02 Thread Bob Aman
 Sure there is (and Google provides it):

   Prototype hosted on Google's servers
   http://tinyurl.com/google-hosted-prototype

 I guess the left hand doesn't always know what the right hand is doing
 in an organization as large as Google :-)

You misunderstand.  I'm well aware of this service, but the vast
majority of the people I've seen with this problem are hosting the
file themselves.  And in most cases, that means we still have to
diagnose the problem and ask them to upgrade once there's an upgrade
available.

   For every user that contacts our support team (and hopefully, gets
 correctly diagnosed and given a fix) there are ten more that give up
 before even talking to support.  Of those ten users, most will assume
 the problem is Google's fault, because the visible breakage happens
 in our code even though the bug is Prototype's.

 Why not enhance (and future-proof!) the Google Friend Connect code,
 right where it fails, to simply check the (by now, already loaded)
 Prototype.Version number, and if it's the version with the bug, throw an
 error which says something helpful like:

   Detected Prototype 1.6.1: This version of Prototype is not
   compatible with Google Friend Connect.  To resolve this issue:

   A. Upgrade to the a newer release of Prototype

   B. Run out patched version of Prototype 1.6 hosted at
      http://ajax.googleapis.com/prototype/1.6-patched/prototype.js

   C. See our http://support.url for more info, and other ways to
      work-around the bug, and resolve this issue.

Hmm, that's actually a good point.  It's a lot less likely to be
brittle and has the desired effect.

 I'm happy to contribute patches or do
 whatever you guys need to make this fix happen.

 Mailing Tobie and Andrew bags of cash, or giving them great-paying
 no-show jobs at Google probably couldn't hurt either :-)

We're hiring, they're more than welcome to apply.  :-)

-Bob Aman

-- 
You received this message because you are subscribed to the Google Groups 
Prototype: Core group.
To post to this group, send email to prototype-core@googlegroups.com
To unsubscribe from this group, send email to 
prototype-core-unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/prototype-core?hl=en