whitenight - 7:31 am on Jan 14, 2010 (gmt 0)

Do you remember waaaay back in late Nov./early Dec when MC told the world that Caffeine was being delayed to "save stress on webmasters before the holiday" and it would be rolled out soon afterwards?

Do you remember what I said was the reason back then?

So here's the question for you, IF as MC said Caffeine was "ready" a month and half ago, where is it now?!

We're halfway done with January...what's the hold up?

As I'm too "lazy" to find the original thread where I pointed out the issues, I'll point to my first and second post in this thread

Are they "testing" or simply screwing up? With the Caffeine datasets being LIVE (ie sending actual and large amounts of traffic) for periods of time, one wonders what the hold up is....again. ..... IMO, The Caffeine infrastructure update is a complete mess right now. (which is probably why they are hesitant to rollout the dataset now) As several threads indicate and I observe, If the old infrastructure is called "Big Daddy 1.0" And Caffeine is "Big Daddy 2.0" (aka superfast indexing, etc) Then, again, after trying to roll out Big Daddy 2.0 in mid Dec, it was such a disaster that they reverted back to Florida 3.0! Which is the nonsensical indexing and updating that's been occcuring for the past month or so.

Psst. I said back in Oct Goog was having MAJOR problems with getting Caffeine rolled out.

It's been over 6 MONTHS since dev.goog was showing Caffeine
(and according to MC in a NATIONAL interview, the engineers had ALREADY been working on it for months before),
you figure it out...

------------------

I'm not even going to go into why the current Caffeine showing is an OLD Caffeine dataset compared to what was shown on Tues and Weds.

Hmm, how would anyone be able to prove that? =P

[edited by: tedster at 12:12 am (utc) on Jan. 16, 2010]