Re: Quantum Computing vs Quantum Physics
Yeah nah. AFAIK the Ising stuff is a description of quantum phenomena, modelled in a classical computer. I think it flies. But I wrote it ;-)
328 posts • joined 5 May 2013
FWIW my focus is now covering Asia and this kind of story is a way for me to introduce the region's big players to readers.
As I was writing it I knew that it was not going to be searing analysis. But I felt it worthwhile introducing readers to China Mobile with something like this, rather than starting to cover its news without background.
And I feel that describing the sheer scale of a company like this, and its growing offshore ambitions, is useful information to readers given the rapid economic and geopolitical shifts in the world today. Its not just Huawei that will make waves!
So a chap I know who worked at a southern fried joint said the recipe for their infamous gravy is: sweep up all the crust granules that fall off the chicken while it sits breeding salmonella under the heat lamp, add water, stir vigorously until it is gravy.
And then there was the time the morning's sweepings hit the floor ....
Not quote your level of mess, but not a good taste either!
But a lucrative pimple: if you are still in the SPARC ecosystem the number of suppliers will keep shrinking and Oracle can keep raising prices ... I've heard of old platforms where the handful of remaining vendors and/or service providers can charge whatever they want just to answer the phone.
We reported exactly what AWS published and none of that mentioned multi-hypervisor strategies. When we saw AWS' posts we immediately asked AWS for comment. As it happens, AWS immediately reached out to ask us for a correction of an unrelated error in the piece (I mixed up cores and threads). So there goes the "AWS is too busy and you don't matter to it" argument.
They know where to find us and are not shy about doing so.
But AWS never asked for any change to either piece regarding the hypervisor content. I was not aware of the TechTarget piece until today and will refer to it now.
We don't aim to be relevant to vendors. We aim to be relevant to readers. And I'm pretty sure they appreciated reading about a significant piece of news here, first, TWO WEEKS before TechTarget touched it.
Nice of them to tell that to Techtarget - as our story states, when we read of the new KVM hypervizor, we immediately asked AWS for an interview about their strategy. And they never replied. Further, their statements to TechTarget contradict the words in their own FAQ, which said all new instance types would use KVM. See our second story for the screen grabs to that effect
Given that the whole point of the NBN was faster, more resilient connections, and every ISP is hitting its customers ASAP once the NBN rolls into town, I think the slow uptake is notable.
FWIW I worry that even a 25Mbps NBN connection would send me backwards from the 16Mbps I've been lucky to have over a 900m cable run for the last 11 years.
Really? For starters, I won't have my byline on native marketing. And it is Just Not Something We Do At The Reg. Indeed, we mark such stuff as PROMO every time. And we do precious little of that.
Secondly, I think you're glass-half-emptying this. I look at it this story as as finding a customer-only communique, pointing out it will mean a forced migration, identifying a market shift and offered some analysis on how this could be a deeper play.
FWIW, when all we have is vaguely-related stock, we have the option to use a tag so it doesn't appear. I do so for most stories. The idea is that if the image doesn't help to tell the story, we don't use it. We also have a size limit on header images to help page load times.
No, my theory is not that these announcements are connected to decreasing sales. I raise the possibility that Cisco, which is on the record in an earnings call and to me personally as saying its converged systems sales are not good enough, might have felt that poorly-integrated data protection could help things along. I put that to Cisco, they deny it, so I am not sure how that comes out as Cisco-bashing.
Reference architectures are pretty dull. The "edge" in the story is an attempt to make them a teensy bit less so.
Ridiculous theories? All I did was ask Cisco if the fact two of these came along at once was a plan. And I do not point out that everyone can do what Veeam is doing with the Hyperflex API. I point out that anyone else >could<, should they choose to do so. In my conversation with Veeam they told me as much.
Biting the hand that feeds IT © 1998–2021