When comparing Knative vs Google Cloud Functions, the Slant community recommends Google Cloud Functions for most people. In the question“What are the best serverless frameworks?” Google Cloud Functions is ranked 3rd while Knative is ranked 4th. The most important reason people chose Google Cloud Functions is:
Cloud Functions, as of this writing, supports JavaScript, Python, Go and Java.
Ranked in these QuestionsQuestion Ranking
Pros
Pro Cross-platform and multi-cloud.
Works wherever Kubernetes works, which is pretty much everywhere. You can use Knative on Google Cloud, AWS, Azure, and even on-premise.
Pro Supports multiple languages
Cloud Functions, as of this writing, supports JavaScript, Python, Go and Java.
Pro Supports multiple sources of events
Cloud Functions can be triggered from PubSub and from HTTP events, for example.
Pro Frictionless to create
There is an inline editor in Google Cloud for writing and submitting/deploying cloud functions, so while it is possible to store a Cloud function as code in a repository you can try and experiment without getting to that point.
Cons
Con More complex initial setup
While setup is easy assuming you already have a Kubernetes deployment and are familiar with Kubernetes, for beginning users who don't have a Kubernetes cluster, starting with Knative is likely to be a more complex undertaking than other solutions.
Con Limited languages and dependencies
Only the set of languages explicitly supported by Cloud Functions can be used; for more flexibility, I would highly recommend Google's other serverless environment, namely Cloud Run.
Alternative Products
