4 ms·

Oh so your personal experience trumps Google's published uptime? Got it. My bad. I am a Google "advocate" but I state facts. My affiliations don't matter.

by ditojim 15y ago

Oh so your personal experience trumps Google's published uptime? Got it. My bad. I am a Google "advocate" but I state facts. My affiliations don't matter. Again, you are off base to suggest I disclose affiliations in comments on a news aggregator site. That isn't even logical or reasonable. If I was a blogger writing a story it would be a good idea to disclose things of this nature, but I'm not blogging. And you're the only one down voting my stuff..

Silhouette 15y ago
> Oh so your personal experience trumps Google's published uptime? If you'd like to give a rigorous definition of that "uptime" figure, I imagine we could work out the probability of my experience on all those different occasions, working with several different groups in several different places, happening by chance despite the true uptime figure still being 99.984%. Right now, it fails the credibility test. That uptime gives you about an hour and a half of downtime per year on average. I don't think we managed a single meeting in the past year without someone in the room having trouble using the software in one way or another. > And you're the only one down voting my stuff.. I didn't downvote you, I replied to you.
- rbanffy 15y ago
  > I don't think we managed a single meeting in the past year without someone in the room having trouble using the software in one way or another. You must have another very serious problem. This doesn't look like any past experience I heard of. I have been relying heavily on Google applications since 2005 and, in those years, had only one minor glitch when setting up my wife's company corporate mail - an account I couldn't create for some time.
  - Silhouette 15y ago
    > You must have another very serious problem. That is possible, of course. However, I would point out that these meetings were attended by a whole team of contractors, each with their own computers configured with their own choice of OS and browser. Moreover, they were held in a variety of different locations, and indeed across several different locations at once via teleconference on some occasions. In other words, it wasn't one very serious problem, it was probably a whole bunch of little problems that caused specific features to be inaccessible to certain locations or not to work properly on specific client platforms during a particular period. (Before anyone jumps in, clearly everyone's Internet connections were fine during the teleconferences, because we were using Internet-based conference software to run them...) My point is only that it's a bit rich to claim a 99.984% uptime based, presumably, on having servers available, if the code that is running on those servers isn't properly quality controlled so that customers can actually use it to do real work. Just because most of the people on the team can connect fine, it still screws up the meeting if a few others can't follow along. Just because people looking at the spreadsheet in Firefox and Chrome can update it, it doesn't help if the guys using IE can't see the changes.
    - rbanffy 15y ago
      To get to the 99.984% number, 160 people out of every million users would have no access to the application on any given moment. The number doesn't look that inflated. Most of the time, our (disclaimer: I don't work for Google, but I host a couple web apps) stuff just works.

by ditojim 15y ago

Silhouette 15y ago

> Oh so your personal experience trumps Google's published uptime? If you'd like to give a rigorous definition of that "uptime" figure, I imagine we could work out the probability of my experience on all those different occasions, working with several different groups in several different places, happening by chance despite the true uptime figure still being 99.984%. Right now, it fails the credibility test. That uptime gives you about an hour and a half of downtime per year on average. I don't think we managed a single meeting in the past year without someone in the room having trouble using the software in one way or another. > And you're the only one down voting my stuff.. I didn't downvote you, I replied to you.

rbanffy 15y ago
> I don't think we managed a single meeting in the past year without someone in the room having trouble using the software in one way or another. You must have another very serious problem. This doesn't look like any past experience I heard of. I have been relying heavily on Google applications since 2005 and, in those years, had only one minor glitch when setting up my wife's company corporate mail - an account I couldn't create for some time.
- Silhouette 15y ago
  > You must have another very serious problem. That is possible, of course. However, I would point out that these meetings were attended by a whole team of contractors, each with their own computers configured with their own choice of OS and browser. Moreover, they were held in a variety of different locations, and indeed across several different locations at once via teleconference on some occasions. In other words, it wasn't one very serious problem, it was probably a whole bunch of little problems that caused specific features to be inaccessible to certain locations or not to work properly on specific client platforms during a particular period. (Before anyone jumps in, clearly everyone's Internet connections were fine during the teleconferences, because we were using Internet-based conference software to run them...) My point is only that it's a bit rich to claim a 99.984% uptime based, presumably, on having servers available, if the code that is running on those servers isn't properly quality controlled so that customers can actually use it to do real work. Just because most of the people on the team can connect fine, it still screws up the meeting if a few others can't follow along. Just because people looking at the spreadsheet in Firefox and Chrome can update it, it doesn't help if the guys using IE can't see the changes.
  - rbanffy 15y ago
    To get to the 99.984% number, 160 people out of every million users would have no access to the application on any given moment. The number doesn't look that inflated. Most of the time, our (disclaimer: I don't work for Google, but I host a couple web apps) stuff just works.