mindrun

Awesome! Let us know if you have any feedback!

At the moment the guides available at https://ronin.co/docs could be used for getting started! We're working on landing a starter boilerplate in the coming weeks (early 2024).

Definitely!

It's a breeze to set up with any frontend framework, but will work especially well with Next.js (built by Vercel).

Only the "Serverless Function Region" feature, meaning being able to select which specific region a Serverless Function runs in, is only available for Pro Teams.

It seems as if this wasn't clear from the UI. Would you agree? It sounds like you've assumed that it's the entire Serverless Function feature that would not be available.

Great suggestion! We'll add a link right after the conference.

Whenever the Next.js + Vercel combo gains a new feature, Vercel ensures that it's available in standalone Next.js too – even when deployed to other providers.

That's true for all the features mentioned in the Next.js 10 blog post: Image optimization, Internationalization, but also Analytics.

Since you mentioned the latter: Did you notice that we wrote a detailed documentation page about how to report those metrics to any service of your choice?

https://nextjs.org/docs/advanced-features/measuring-performa...

Sure, there's obviously a whole UI piece to this as well – but since you interact with Next.js programmatically and there's a quite sophisticated data storage that needs to back all of this as well, Vercel optionally provides you with a pre-built solution.

But again, to be clear: If you want to use Analytics + Next.js elsewhere, Next.js supports reporting them natively – even if not hosted on Vercel.

I'm glad to hear! Over time, more and more guides and proper documentation will be created for Now 2.0, so I'm sure you won't have any troubles with migrating any kind of application to Now 2.0. Aside from that, your bill is most likely going to decrease heavily, as Now 2.0 is much cheaper than Now 1.0.

This release of `now dev` is indeed a preview release. We're working very hard to improve the quality of the CLI, so should you notice any bugs, please let us know and we'll get right to it: https://zeit.co/feedback/dev

Hey, Leo from ZEIT here!

I agree strongly. There's been a lot of chance over the last couple of months, as Now 2.0 appeared and the entire platform started adapting to it.

However, I'd also like to let you know that the entire concept of "platform versions" is just a temporary way of slowly allowing everyone to migrate to Now 2.0 at their own pace. Once this process is complete, the whole concept of platform versions will disappear and I hardly doubt there will be any major changes from that point on.

Thanks for the compliments! That's exactly what our product is trying to achieve: Abstracting away all of that low level stuff, so you can just run `now` and that's it.

The command used for this can be invoked on any OS that Now CLI supports (Linux, Alpine, macOS and Windows). In terms of the languages that are supported, there's no end, really:

https://github.com/zeit/now-builders/tree/master/packages

(These are just the default ones, you can add your own language using https://zeit.co/docs/v2/deployments/builders/developer-guide...)

Thanks for your feedback. We've actually received quite a lot of other feedback regarding the new pricing model and will – as a result – soon be working on a way to set custom alerts and limits, so that it behaves just like 1.0 pricing, if you want it to.

With regards to 1.0 "just working": Aside from making 2.0 more intuitive, we're heavily investing into tools that allow you to automatically transition existing applications to 2.0, so that would definitely help a lot.

I'm glad to hear. Should you encounter any bugs, please let us know at https://zeit.co/feedback/dev and we'll get right to it.

I love what they're going for! However, I really don't think that text messages are the future. Looking at things like WhatsApp, iMessage, FB Messenger and others, a company like Apple will probably drop support for them very soon. A possible fix for this would be to support 2FA apps like Google Authenticator for communicating those codes. If not, I'm more than sure that Apple will release some kind of API for services that allows us to send messages...