At least that's what the latest rumors are saying.
29 replies (most recent on top)
Hope so
Seems like your rumors were wrong.... 6/19 and I've not seen or heard anything yet to make me believe its coming. Plus the stock price is doing quite well.
For those who might consider @qoop+1mxaXTCf to be useful, lets examine the response in more detail:
What would I get by shitposting on the MS or Amazon boards? Those companies already have jaded engineers. Google engineers are far more supple.
Right here, the poster's motivation is simply trolling. He or she is not adding anything constructive, and tacitly acknowledges such.
"Citation?" You sound like someone who'd ask how a red black tree works at an interview. Or explain the busy beaver problem.
This is evidence that the poster simply can't answer the previous inquiries. And by mocking the request for data, it is further trolling.
Yes, AWS has outages. It lasts for at most a few hours, and the issue is resolved. From the news GCP France's outage lasted for weeks.
The only long-duration outage was in a single zone.
No big cloud provider recommends running your service in a single zone. For that matter, none of them recommend running in a single region (just ask those who run their services in just us-east-1 at AWS, and how they feel about the nearly-annual region outages).
This is how I guess GCP was started: a bunch of engineers/directors sitting around eating gourmet lunches and coffee funded by the lucrative ad business and thinking, "Wouldn't it be cool if we had something like AWS? Surely since we have tougher interviews, we'll be able to make something better."
This is a bizarre non-sequitur that is more evidence of trolling intent.
@qnii+1mxaXTCf "Citation?" You sound like someone who'd ask how a red black tree works at an interview. Or explain the busy beaver problem.
What would I get by shitposting on the MS or Amazon boards? Those companies already have jaded engineers. Google engineers are far more supple.
Yes, AWS has outages. It lasts for at most a few hours, and the issue is resolved. From the news GCP France's outage lasted for weeks.
You can check for yourself how much GCP charges for VM-VM egress interzone traffic within a zone in a region. This means that GCP is charging for traffic over a cable patched in the same building.
You're asking for "citations" because what I said sounds outrageous. But that's what GCP is. This is how I guess GCP was started: a bunch of engineers/directors sitting around eating gourmet lunches and coffee funded by the lucrative ad business and thinking, "Wouldn't it be cool if we had something like AWS? Surely since we have tougher interviews, we'll be able to make something better."
Clearly you don't know what a citation is, because nowhere in your rantings is there a citation.
Also, you haven't confirmed that you shitposted about OVH when they had their fire.
Also, you haven't confirmed that you shitposted about Amazon for their various us-east regional outages.
Also, you haven't stated that you will shitpost about Azure when the same thing happens there.
But go on. Continue pretending that you can run in one region and everything will be perfect.
@mcrq+1mxaXTCf In AWS/Azure AZs in a region are in different building. So for reliability, you can run on multiple AZs within a region if that suites you. If one AZ goes down within a region, the other AZ is not affected. If you want lower latency, you run in multiple regions. If you want dedicated traffic across AZs you are charged for it.
In Google, there are multiple zone within the same building. This is misleading to how we think about "zones." Therefore, if one zone goes down, multiple zones could potentially go down, which is what happened in France. Furthermore, GCP charges for traffic within zones that are in the same building, which makes no sense.
Amazon needs AWS to stay profitable. GCP is just a side project for Google because of their more lucrative ad business. I've heard that Google's own services don't run on GCP, whereas in Amazon, all services are deployed on AWS, not prod. Who is going to do a better job with their cloud? There's no reason to use GCP.
@lzij+1mxaXTCf your response is a complete non sequitur to what I wrote.
I said no cloud provider say single zone reliability is 100%.
For that matter, they all suggest going multi-region.
As for the rest of your post:
- Citation needed, and make it a citation from someone that knows what they are talking about
- Did you shitpost on the OVH forum when they had a fire? How about Amazon for their various us-east regional outages? Do you promise to shitpost over on the Microsoft board when the exact same thing happens to them?
Quit pretending that running your cloud services in one location is a responsible thing to do.
Spoiler alert, none of the big cloud providers say that.
When AWS and Azure advertises an availability zone, they mean a different building. A Google "zone" is in the same building, which explains why in France when one zone went down, it impacted other zones. What's more is that Google charged for traffic between zones. The fine print probably explains all of this.
The only reason to sign up for GCP is if you are enamored by Google's mystique, which has eroded because of their performance and layoffs.
I would also say Google would be what Yahoo is right now if they hadn't acquired Doubleclick. Google gives the impression they've made so much money because they have the smartest people, but they are like any large company throughout history that grew by acquiring smaller companies. I don't think there is a data center/cloud startup right now that would boost GCP in the same way Doubleclick boosted their ad business.
Google did better than expected, but it didn't do well, which means it's all downhill from here.
This makes absolutely zero sense. A failure to greatly exceed Wall Street estimates does not mean the company is a failure.
Google Cloud was profitable last quarter for the first time ever. It is unlikely it will be profitable again considering the economic downturn, and with the revelation that Cloud is not reliable because of the recent outage in France, which revealed they falsely advertised their data center topology.
A couple of points are here. First, it appears your hypothesis is that the first profitable quarter coupled by a follow-on economic downturn spells doom. Rebuttal: Google, itself (at the time search) was unprofitable until 2001Q4. As I recall, there was a big economic downturn starting right about then. Yet Google is still here, decades later.
You are also going to have to do better about claims of false advertising. Nowhere did Google say "yes, just run your service in one zone, it will have perfect reliability." Spoiler alert, none of the big cloud providers say that.
@3dnr+1mxaXTCf lol you are giving way too much credit to an I/O with that damn duck
Do you really need to discuss about Fitbit? Everyone knows is a POS and full of politics. If you dig into the leadership you will see the majority of them came from failed or canceled projects. Fitbit is just one more for theirs list. If you are not in AI or any profitable division, you are in serious risk for the new layoff. Of course a new layoff will come soon.
@6hog+1mxaXTCf So it seems like I'm right. Google is an ad company (via acquiring Doubleclick).
So much effort, ingenuity, etc. put in just to display an ad.
@4mkq+1mxaXTC Azure? Lol
@6oes+1mxaXTCf are you even a Googler? Anyone with sufficient tenure wouldn't be asking those questions.
@4bsw+1mxaXTCf Is search separate from ads? Without ads, search brings in no money. Because there is so much overlap from both software and business perspective, I would expect they would be in the same division.
YT is also exists mostly because of ads. There's YT TV (it's hard to believe people pay more than $65 for it).
There's no reason to use Google Cloud other than if your team made the mistake of using it in the first place.
Google News will be impacted. It’s simply not profitable and a waste.
I do not agree about San Diego team being a good team. They are copy and paste engineers and they would easily replaced by ChatGPT .. .LOL....
@4zos+1mxaXTCf the argument made in @3jvy+1mxaXTCf doesn't rest entirely on that one parenthetical.
And you know that. But you couldn't argue against any part of the argument, so you feign indignation and resort to ad hominems.
"at least one person I am aware of is starting retirement a couple of years early" and who cares ? what about several people that left their jobs to join this messy Google and were fired few months later. You should be a brown nose and you will be laid off too. Nothing is forever bozo.
Google did better than expected, but it didn't do well, which means it's all downhill from here.
Google Cloud was profitable last quarter for the first time ever. It is unlikely it will be profitable again considering the economic downturn, and with the revelation that Cloud is not reliable because of the recent outage in France, which revealed they falsely advertised their data center topology. There's no reason to choose Cloud over AWS or Azure.
my bet it will be in June 23 because it is a Friday. If the layoff happens of course, but if google follows the trends like Meta and Amazon, more layoffs will come. No question about people involved on AI, it is way safer for sure IMHO.
Search, ads, YouTube and now cloud
Is any division profitable beyond ads?
Fitbit division is not profitable. One thing is the company profit and another thing is a specific division. The team in San Diego is really good but the leadership is not and does not have idea what they are doing. I met an L7 program manager that things buganizer is all we need with some automation to release a product. No strategy, totally disconnect from real daily issues, poor product features and horrible hardware design. The Fitbit is one of the worst division, if not the worst, to work for. Run... Just ... Run
More absurd speculation from people pretending to be insiders.
A couple of weeks back, someone boldly predicted that the earnings results would be poor this cycle, and there would be more layoffs announced by the end of that week. In reality, earnings were better than expected, and no additional layoffs were announced that week.
The only thing that is vaguely spot on is the comment about Fitbit, and purely by accident: The January 2023 layoffs have left some Fitbit employees without a permanent role, but they are being kept on temporarily to hand over work (with a completion bonus significant enough that at least one person I am aware of is starting retirement a couple of years early). Some of these employees will be offboarded in June, but those won't be because this post is correct -- they are part of the January layoffs, not of a new June layoff.
the Fitbit division will be heavily impacted for sure. They are failing in releasing the products and this last google io did not even comment on any new smartwatch... it means they are failing. I heard it is the worst place in Google to work and should be avoided at all cost. Anyone working there, I would move to a different division asap.. it is a very risky division. The Google Fitbit pixel is a joke compared to the competitors.
July 4 is a holiday. June 19 would work though.
Why don't they save it for 4th of July? It would be more appropriate.
If you know more, please share.