I am sorry but the concept of "Beta release level" is a complete misfire/mismatch for what an enterprise needs. For example, you cannot, on one hand, advertise that you have a competitive feature (Google Functions competing with AWS Lambda), but then, on the other hand, turn around and label it beta and basically use that an an excuse for inferior reliability and inferior documentation. How can you basically GA a major piece of platform functionality, call it beta, and then ask any enterprise (that has lower risk tolerance) to use it? Enterprises don't want to invest into beta-labelled features, because they know it's an excuse for bugs and half-baked support. No wonder GCP is struggling for adoption.
("beta release" level is a conversation you have with select trusted partners that are willing to tolerate your early stuff in exchange for early access to value... it is not something that is acceptable to advertise as open enrollment to all)
Flow, Teams, Lists, Planner, Sway, Stream, Forms, Kaizala...
Sorry, but these aren't battle tested enterprise apps at all. Could as well pull random apps from the Google store.
Whenever something new releases the first reaction already is "not again"...
Anyone who uses GCP knows you type “gcloud beta ...” an awful lot. But enterprise sales are made on the golf course between people who have never and will never use the product themselves.
This is all obsolete anyway, since GCP has announced they're moving to two stages: Preview or GA. That's it.
https://cloud.google.com/blog/products/gcp/google-cloud-gets...
My point was that features were being advertised as essentially GA that were not actually GA. When evaluating the Google Cloud Platform sans-beta features, I was suddenly looking at a much more barren offering, in comparison to AWS.