I would not over-read into that doc. In practice, the only missing stuff are extreme edge cases of the type that is actually not consistent between other implementations of bash.
In practice it works great. I haven't seen a failed command in a while
The big difference is how the microvm is utilized. Lambda reserves the entire VM to handle a request end to end. Fluid can use a VM for multiple concurrent requests. Since most workloads are often idle waiting for IO, this ends up being much more efficient.
Part 2 is that you can also use an actual server if your workloads happens to be predictable (or is partly predictable). That gives you better cost efficiency for that part of the workload
We're embracing copy-and-paste with the product rather than increasing abstraction. The tool provides the HTML or React code for building the generated UI. The way you actually use it, is by copy-pasting it into your app. From that moment on your workflow and specially debugging workflow is exactly as before. The tool just writes the first 100 lines of code to get you started with a great UI.
New generations are behind a waitlist, but you can see what the service does on the explore page (and bottom of homepage linked above) https://v0.dev/explore
- You can turn this on without changing the code of your site (just need to activate emitting the metadata in the CMS)
- Supports any framework
- We're working on an open content-source mapping standard that makes the underlying tech available to any CMS, e-commerce system, or other content source.
The editing functionality is delegated to the CMS. Respectively content changes flow through the exact pipeline as changes originated directly from the CMS would. In fact, we allow the CMS to completely control the actual editing experience.
The main point of this feature is that if an employee does find a typo on some article, they can just fix it rather than going to the CMS, finding the actual place where that text is stored, making the change, etc.
Yeah, if you go into the dashboard it gives you a bunch of options for connecting to the DB including the names of the automatically generated environment variables. And that includes POSTGRES_URL which most tools default to.
I'm super excited in graphing this over time. Will be interesting to see how the providers develop over the coming months.
FWIW we also need TTFB not just tokens per second. The first token is key for UX
<Vercel CTO> So, why this price is there is complicated within the way this marketplace works. In practice, you talk to sales and these figures are irrelevant.
From the page: For custom pricing, EULA, or a private contract, please contact [email protected] for a private offer.
<Vercel CTO here>
It does not mean this immediately. We're currently working with some clients on hybrid solution where a very limited feature set is available in a government context, but the full Vercel feature set is not yet available in AWS Gov Cloud. Definitely happy to have a conversation about it!