I've been reading through the docs and skipping through the one recentish YouTube tutorial trying to make sense of what this actually is. While it seems like an

I've been reading through the docs and skipping through the one recentish YouTube tutorial trying to make sense of what this actually is. While it seems like an impressive thing for what appears to be a one-man-project, the almost complete lack of documentation makes it feel like a bit of a hard no in the current state. There seems to be a history of it being heavily linked to Web3 things that also feels weird. Some suggestions for this to be able to succeed: - Documentation, documentation, documentation, the only place where I could that the three supported ways to write a serverless function are with Go, Rust and AssemblyScript is somewhere hidden in a tutorial. It all has to compile to WebAssembly so I guess that's the limiting factor. - Examples? - Using git as source of truth for the configuration/state of a system is cool. Please link to sample repos so I can see what a system with a website, some functions that touch DB and files, and the configuration etc looks like. - How does the database part work? Client SDKs? - There are lots of protocols with unclear names that are only briefly mentioned here but then seen in random places in configuration: https://tau.how/01-getting-started/01-local-cloud/#protocols https://tau.how/01-getting-started/01-local-cloud/#protocols - The Concepts part of the documentation is buzzword soup, it's impossible to derive any meaning from it other than that the author dislikes Kubernetes and probably used some generative AI for the content. - Roadmap, plans, versioning, plans on how Tau version upgrades should go, ...