nitric

ram made things even less clear because it showed actual shapes flowing over the wire. Is it generating a SVG...? But no, the next example is a database... migration...? That shows... a user being added, but returns a table? Thoroughly confused now =/ An I migrating a schema, adding a user, or querying a table? At this point I still didn't know what the actual service was... Then the storage example was also confusing, not showing any way to specify the cloud being used (is there a cloud?), where the image comes from (what is imageData), and what is .file... is it a filename, is it a blob of some sort that's being overwritten, what is a "profile" anyway, and why can I define its permissions at the same time I'm writing to it...? And still not clear what this service even is. Fortunately, then I found the Github link at the top: https://github.com/nitrictech/nitric THAT was much clearer, IMO. "Easy infrastructure from code". Aha. So it's an infrastructure orchestration system that spins up and manages cloud services from code? That instantly made sense. To me as a dev, something like "Orchestrate cloud infrastructure directly in code. Any cloud, same syntax." would be a lot clearer than "Next generation cloud development... building blocks for modern apps", which can mean anything from a web host to a UI lib to a nocode platform to an IDE, etc. Maybe I'm just over-literal, but I honestly couldn't tell what the home page was trying to say... for a while, I actually thought it was a placeholder page for some generic SaaS example, not an actual product. Everything was too abstract that I didn't think they were real examples. In my mind, the service is something like a Dockerfile or CI/CD pipeline or Lando.dev – something that abstracts essential services in a provider-neutral way, and in code instead of config – but I didn't get that at all until I read the Github. I get that you're probably trying to make the home page examples super concise and simple, but without seeing a realistic workflow, it was really hard to understand what was supposed to be happening. For example, having a realistic API example that does something relatively normal (authenticate a user, or send an email, or query a DB or whatever) would be way clearer than a "greeter" that returns a "square". I think that some before/after comparisons might help too, e.g. "here's what uploading a new file looks like in nitric, vs using the AWS/Azure/GCP SDKs directly". Like an apples-to-apples comparison of what it'd take to spin up an account, manage the permissions, provision the instances, wait for them to boot, see their status, specify the tokens, convert some binary blob, upload it, see the results, etc. I hope that didn't sound harsh? I was trying to share my actual impression as a first-time user, which was confusion followed by eventual understanding following by "this is actually pretty cool... I hope it gets more popular/stable!"

of innovative ideas. Fortunately, there are a few new tools that can help address these problems. For instance: - Plutolang: https://github.com/pluto-lang/pluto - Winglang: https://github.com/winglang/wing - Nitric: https://github.com/nitrictech/nitric