I think you may be misreading the situation. When Anthos was announced, it didn't exist yet. They didn't have anything to sell you and you weren't important enough to be trusted with that knowledge. In this regard, your comparison was probably apt (especially if you were inquiring about Watson).
Released, not announced - they actually contacted us about it and then ghosted when we asked for a quote. At the very least I’d have expected a simple “we’ll get back to you”.
IBM was similar: we were trying to buy Opteron servers, let our rep know, had a bunch of people show up, ended with them saying they’d send us a quote, no reply to multiple requests. Maybe they weren’t interested in mere 6 figure purchases but they could have said so.
(And, sure, we aren’t the biggest customer but you don’t get large deals if you can’t handle medium size deals. AWS shows up & they get considerably more business.)
What would be the logic behind “deaf”? That “mute” is a homonym/polyseme of a word for a disability, so let’s just use the first letter of any disability?
Zoom at least uses Cmd+Shift-A for Audio and V for Video
But as the recent Google Icon kerfuffle, UI/UX is not their strength (probably because of opinionated technical people that think you need to A/B shades of blue)
Teams uses something equally silly, like Ctrl+Shift+M for mute/unmute, IIRC.
Which is pretty annoying, because the mute button is about the most important button in a videoconferencing tool, and I want to have it under a single keypress, so it can be used effortlessly, with my left hand (the same that operates Alt+Tab, while my right hand is on the mouse, scrolling ... well, meeting agenda, let's say).
I'd fix that for myself with AutoHotkey, but I can't, because Teams is just another Electron app, so I can't just look at which UI component has the focus to create a rule, "if focused on Teams video call and not its chat, rebind M to Ctrl+Shift+M".
One of the countless reasons I hate it when people do custom UI, instead of using OS-provided controls.
Cloud Run is compatible with the Knative open source project, so you should be able to take your apps to a different cloud like you would with Kubernetes.
Although a public IP address is required, you don't need to poke any holes in the firewall. As a result, it is not a problem from a security perspective.
According to [1], the standard quota is 1,000,000 invocations per 100 seconds and can be increased. Maybe try asking again for increased quota? If the documentation is incorrect, please file an issue [2].
Counter-intuitively, ending the response before processing the data may actually be hurting your p99 response time. According to [3], instances which are not currently handling a request get very little CPU and generally don't make any progress. This means that this work will still be waiting to be done when the next request comes in and can slow it down. You may even end up with an instance trying to process several requests' data and also trying to handle another request on top of that. This last request is going to get an overloaded instance and likely be very slow. Further, the function isn't guaranteed to ever be run again, so that deferred work might not even ever happen.
It probably will cause you to use more of your invocations per 100 seconds quota, but you really shouldn't start background processing tasks in a Google Cloud Function that continue after completing a request.
I have paid support. It's socket connections we're hitting super quick.
Interesting and thanks I had no idea on the end response CPU time. It's just storing the json to Google Cloud Storage but it does take 100-300ms it seems!
