tweenagedream

Who says you have to purchase a service with dollars?

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.

Can you please link to the incident where the "full region" was down for weeks?

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

I work at Google so am perhaps biased, but that article is from 2019 and cloud is now a 20B/yr business and growing. Why does it keep coming up?

Usually a connection is defined by what's called a 5-tuple. Source up, source port, dest up, dest port, protocol (e.g. tcp or udp)

I think down leveling is quite common, especially at higher levels as the expectations grow quite a bit between senior and staff. Depending on the position, actually filling it with +/-1 of the target level is a win. Interviewing is expensive and if a candidate is good for the role, but perhaps just a bit below the bar, then a recommendation to hire at L-1 tries to keep the candidate and give them a career path.

This is from my perspective at Google, I've never worked at Amazon.