I am developing something similar with effe [1] and effe-tool [2] (completely WIP), that are suppose to be an open source implementation of AWS lambda. I am fa

I am developing something similar with effe [1] and effe-tool [2] (completely WIP), that are suppose to be an open source implementation of AWS lambda. I am facing problems similar to the one of the author, and I can see why he made some choices but I disagree on most. In my opinion we should aim to a tool to build single executables and another tool to package those executable in a docker container. Also I am doing my best to have as little as possible configurations, configurations are needed to deploy your application, and deployment is a different kind of problem. I must say that is HARD, mainly for the constrain of go. I would love to attach metadata to a go package, configuration would became a no-issues. I would love to build my packages in a dynamic way, eg. these file is the scaffolding, those other are the custom logic, go compile and create a single artefact. However this seems impossible. Go is a nice language but its tool really kill creativity. [1]: https://github.com/siscia/effe https://github.com/siscia/effe [2]: https://github.com/siscia/effe-tool https://github.com/siscia/effe-tool