On: Next.js 12

[jekude]

This certainly is akin to what I had in mind, and looks really great. A couple of thoughts:

1) Ideally the framework is polyglot (Go seems sensible though)

2) I wish they had queues/events that were wired up to functions

3) Not sure if using autoscaling k8s services under the hood as opposed to serverless functions is the right choice

4) A bit too opinionated on DB/Auth (maybe I don't want to use Postgres)

5) With all of the above you could get really great end-to-end integration tests as unit tests that I don't see them taking advantage of

[eandre → jekude]

Thanks for the feedback! (I'm the founder of Encore)

Your thoughts are very much in line with where we're going. We're working on natively supporting queues, pubsub, object storage, etc. Our roadmap is available at https://encore.dev/roadmap which should give you an idea.

We definitely intend on supporting more storage options. We already do provide end-to-end integration testing out of the box that integrates with Go's built-in testing support.

The authentication should be pretty flexible; was there something you were thinking of that makes it too opinionated or inflexible?

Thanks!

[pscanf → jekude]

I guess https://dapr.io/ could also be considered a contender in that space, though the developer experience is not as polished as next.js (yet?).

[Zababa → jekude]

> 4) A bit too opinionated on DB/Auth (maybe I don't want to use Postgres)

This feels like a weird criticism considering Next is React only.

[jekude → Zababa]

I think your criticism of my criticism is fair. Perhaps this is somewhere you simply cannot provide a clean abstraction and need to be opinionated.

[Zababa → jekude]

I think that's the case. On the other hand, at a very large scale you may want to move out from Postgres while React can still be fine. I'm not sure if people change more often frontend frameworks or databases.