cramforce

Author here. Let me know if you have questions!

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

[Disclaimer: I made the thing]

In practice it is actually extremely fast because there is no process fork. You're talking nanoseconds for common commands

[Disclaimer: I made the thing]

The initiative is really focused on our current workloads like APIs, SSR, etc.

It definitely makes Vercel suitable for a broader set of workloads, though!

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.

Displaimer: CTO of Vercel here

That's 1 part, yes!

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

Displaimer: CTO of Vercel here

Author here. Let me know if you have questions!

Co-author and CTO of Vercel here. Happy to answer questions!

<CTO of Vercel here>

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

<CTO of Vercel here>

- 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.

Yes! Any postgres and redis client will just work. And the blob store has a REST API.

There are a bunch of examples here https://vercel.com/templates/ai

There was a problem with some models. I went ahead and fixed them.

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 awsmarketplace@vercel.com for a private offer.

You can email my first name at our domain!

<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!

I think these are all good concerns. Where FdI runs counter to lock-in is applications do not "know" the target platform (as in they don't hard code any dependency on the platform). Respectively, the app is staying portable to every target that the app can deploy to.

The way we handle it is to provide a "runtime" within those environments to normalize behavior along the lines that the framework expects.

Yeah, good question. For stateful infrastructure the way we are exploring it is basically like: "Hey, it looks like you expect to talk to a database and we've never seen this before. Would you like us to make one?" …and then going forward the mapping is persisted.

Author here: Happy to answer questions about the post!

The Turbopack project is led by Tobias Koppers, creator of Webpack

If you have no alt attribute, then screen readers read the URL!

Empty strings are the way to go for decorative images

Disclaimer: Chief Architect @ Vercel

This is a good summary. Edge Functions bring another set of trade-offs into the mix:

- Startup-time so fast that if you hit a "cold start" it is still fast enough from a human perception (often <30ms attributable to startup)

- Global by default

- Cheaper on a per invocation

- No limits on concurrent invocations

BUT

- Restricted API set, no node.js API support like Buffers or filesystem access

- Smaller max binary size

- Lower available CPU quota per request

- Lower max RAM usage

- Lower CPU-

It's super trivial to outsource the sub setting to Google Fonts. Just request their CSS and curl the font files referenced in it. If that is too tedious, build a small proxy.

Here the definition is actually broader than FOUC just for the font part. It can cause rendering without any CSS

Do not use this, use Google Fonts, just self-host them. This site claims better privacy, but does so using the wrong solution since you still have to trust them.

Self host (supported by Google Fonts but not by this service): - Better privacy - Better performance (no extra DNS lookups, TLS connection)

Their default embed code is a CSS @import directive. These must never be used in production code (It's fine as a directive for the compiler for local files but not with remote URLs). Leads to FOUC and FOIT.

Also, next step in amateur hour: They serve their CSS and fonts on the same domain as their marketing website. Cookies galore.