Hi Rodric, Have many thoughts on this having just experienced them all when mapping our OW "runtime contract" to Knative... but first would ask a couple of things based on your historic knowledge...
M1) Do you have a specific use case which highlights the issue (i.e., caused you to think on this at this time)? M2) what was the intent of the separation of between init and run (esp. as it seems other impl.s of Serverless like Knative are moving to single exported entrypoint). Will there ever be a "re-init" to reuse a runtime (framework). Will we explore a V8 Isolates approach? 3M) It seems knative thinking is 12-factor app... everything in ENV of container whereas, as a functions (as a workload) developer would hopefully attempt to perform their task without any environmental (OS) awareness ans strictly remain within the function scope. Should we not seek to re-enforce the Serverless differentiation? or give into the notion that functions are just "baked into" Containers. After our knative work, I was actually thinking that init and run distinction should go away as init serves little purpose... that we should endeavor to have a unified container proxy that was a single point enforcement/data massaging for all runtimes (seemingly moving in this direction naturally anyways). Then use the container proxy to explore new use cases uniformly (e.g., other protocols, etc.).
