I mean they did say almost no breaking changes, depending how much has changed in the language, a small handful of breaking changes in niche use cases may be considered almost none by some. I'm not sure I would say the comment is absolutely inaccurate.
I experienced this just last month! Except, I didn't know it at the moment. I was participating in a design review while wfh on meet. We were having some good discussions, which I participated in. Partway through the meeting I start to fidget a bit and unplug my mic, untwist it from my headphone cable and plug it back in. Next time I unmute, unbeknownst to me, everyone else starts hearing the local radio station. I was using a schiit fulla DAC, and one of its features is auto gain on the microphone. Well I apparently didn't plug the mic in enough and it picked up the local radio station and then boosted the gain enough that it came through loud and clear over the call. Blew my mind once I learned wtf was going on. Embarrassing in the moment as I was muted twice and told to stop listening to a podcast during the meeting.
This is because of the way tcp congestion control works. In order to achieve higher speeds, tcp has a "window" that grows, essentially the amount of data in flight, that has not yet been acknowledged by your client. That window doesn't open very wide in the 100kb test because it happens so quickly.
I don't think that is true. MKBHD just came out with a video demonstrating using a video wall that updated in sync with the camera frame rate. Allowing two cameras to see different backgrounds, e.g. two different colors or even two different images, as the demo was showing a parallax effect.
For gRPC, the protobuf is the API specification, a service definition with endpoints, what requests to those endpoints should look like and what responses look like. Of course, there are better and worse implementations, e.g. a well commented proto definition explaining what various args do, etc.
In gRPC the definition is a requirement to use, so at the bare minimum you have the typed structure of requests and responses. There is no such requirement for REST
Because Google no longer knows how to do customer/developer engagement just as it goes into things that require it more?
It doesn't help that it allows others to push opinion pieces in media that build up memes against its products (I honestly believe it's non-trivial part of what killed Google+ - at some point someone believed at Google about it being "ghost town" and started making it more FB-like and pushing "new people to observe" at you, making it less and less usable).
The infamous "will kill your account on basis of unaccountable algorithm and you can't do anything about it" is another big issue when trying to get clients on GCP. I honestly find GCP to be the best cloud I can use when not going full hog on things like AWS-specific services, yet there's always the fear that Google will just kill the account, possibly shuttering the business.
Presumably because the article linked above says that the rumoured deadline for gaining sufficient market share is this year? Also, yes revenues have been growing, but is GCP profitable after all this time? As you point out, it's been 4 years since that article was published.
There’s a bias here for AWS because they were the early adopter product and have traction with startups.
I think Google is more creative on the business side with GCP and is doing well in the market in a lot of ways. AWS does the circa 1985 “Hi, we’re IBM, fuck you” thing.
Azure doesn’t get the grief GCP does because MS service growth is driven by really complicated deals. Few of the types of people who post here understand it.
Lol. Those account managers these days get purged pretty quickly. MS isn’t Oracle, but it isn’t 2003 either.
“It would be a shame if those O365 E5 went up 30%. How about you buy 50% of your spend on these credits that fell off the truck, and we can forget about that?”
According to https://support.google.com/pixelphone/answer/4457705?hl=en pixel 5a is getting eol this month, with the next security update dropping for pixel 6 starting in October 2026
"Last gen" pixel 8 is going to get android and security updates through October 2030