[CGamesPlay]

This argument doesn't really make sense.

> That means a whole lot of CPU that you need to burn during build

This doesn't makes it hard, and I'd rather spend the CPU once than at every edge server on first request.

> uses up loads of storage (that you need to ship to your static web server)

Uploading to S3 (for example) is free, and the edge servers need to store the images anyways (because they are slow to generate as you just mentioned).

> your 60 seconds deployment into a 30 minutes deployment (or longer), that doesn't scale.

Says who? It's a static site so it's not being updated every 30 minutes, and with some intelligent incremental compilation I bet it would remain fast even for the largest sites.

[wereHamster]

When I said hard, I didn't mean technically. I meant it's hard for Next.js to decide how to solve the problem so it works for everyone. I'm doubtful if it even makes sense for them to try to support every possible use case.

There are solutions available to all of these problems today. You can pick the ones which you prefer or fit your workflow.