Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Next.js 12

nextjs.org

Post reply on HN
Print view View original

131–140 of 293 posts

Re: Next.js 12

#131

Post by city41 »

swyx wrote: post #119
jekude wrote: post #48

If Next.js + Vercel is the leader of the production-ready frontend-as-a-service space, why hasn't a similar leader emerged in the backend-as-a-service space? I would love a clean Vercel-like abstraction on top of standard cloud primitives (functions, queues, events, workflows, etc.) with everything wired up nicely and focused on developer experience. It just seems like AWS is so configuration heavy that it is ripe fo…

https://supabase.io has: - Postgres DB (+ admin panel + realtime sync + search + workflows) - Auth - Storage - Functions (beta) (disclosure: am small angel investor) its interesting that you consider workflows a "standard cloud primitive". what do you currently use? (i work on a workflow engine myself)

As far as I know, Supabase is unique in this space in that you really are given a postgres db. You can log into it with any postgres client and do just about anything you want. Combine that with its "backend as a service" layer of niceties and it's a really potent combo.

Re: Next.js 12

#132

Post by fillskills »

leodriesch wrote: post #98
jekude wrote: post #48

If Next.js + Vercel is the leader of the production-ready frontend-as-a-service space, why hasn't a similar leader emerged in the backend-as-a-service space? I would love a clean Vercel-like abstraction on top of standard cloud primitives (functions, queues, events, workflows, etc.) with everything wired up nicely and focused on developer experience. It just seems like AWS is so configuration heavy that it is ripe fo…

I would suggest render.com and fly.io if you’re looking for something that has a similar deployment experience to Vercel.

+1 for render. Great experience so far building an airbnb like marketplace on top of their services

Re: Next.js 12

#133

Post by adam12 »

letmeinhere wrote: post #73
chrisco255 wrote: post #53

Earlier quoted context omitted.

Vercel / Next.js does function as a backend, too. You simply add an api folder and create 'routeName.js' files in there and you've got an endpoint backed by a lambda. And Vercel itself allows you to install backend services such as Redis caching, databases, or queues that you can pull in from those functions.

but (at least last I checked and from what I can glean from current docs) Vercel doesn't host databases, or integrate on a network level with the major cloud providers that do, so if you run your "back end" on Vercel you still need a "back back end" from a different provider and are opting into a huge amount of network operations burden to securely connect the two.

You might be able to use GunJS for your database (decentralized). https://gun.eco/

Re: Next.js 12

#134

Post by benatkin »

r6203 wrote: post #18

I don't get it. It's still not possible to use next/image (without some fancy loader or 3rd party service) when exporting a SSG build. Are people really not using responsive images when exporting a static site? Seems quite ridiculous to rely on some 3rd party service for image optimization when the images could be generated locally when exporting the site...

It's similar to generating compressed files with the build. I think it belongs on the web server layer.

Here's an open source, self-hosted one, that should be easy to integrate with Next.js:

https://github.com/willnorris/imageproxy

To define a custom one, you need only provide a function:

https://nextjs.org/docs/api-reference/next/image#loader

Re: Next.js 12

#135

Post by sbacic »

jekude wrote: post #48

If Next.js + Vercel is the leader of the production-ready frontend-as-a-service space, why hasn't a similar leader emerged in the backend-as-a-service space? I would love a clean Vercel-like abstraction on top of standard cloud primitives (functions, queues, events, workflows, etc.) with everything wired up nicely and focused on developer experience. It just seems like AWS is so configuration heavy that it is ripe fo…

I'm using Hasura for that right now to handle the API + database part. Fairly satisfied with GraphQL API generators so far - they get the ball running quickly and take over the boring CRUD parts so that I don't have to.

Re: Next.js 12

#136

Post by no_wizard »

This is really amazing, is the end result here that they are ultimately opting out of webpack in favor of SWC? It also compiles modules and such. Will have to take a look at the underlying infrastructure here!

Interestingly I think that’s the major win of SWC over esbuild: you get a Babel like plug-in ecosystem for AST transformations and such. Downside: there currently isn’t a way to run asynchronous transforms, much like you can’t with Babel (easily anyway without some subprocess hacks)

I love Vue, but it’s forever married to the Babel parser unless Evan moves over to using SWC for compiling SFCs, which would be awesome but he has signaled multiple times he doesn’t see the Vue Compiler ever being rust based, so it would be reliant on the Vue core team (though I think this is mainly his work) porting the SFC compiler to using SWC underneath.

JSX frameworks won’t have this limitation and can get this massive speed gains and energy without such work. I could see Stencil and SolidJS adapting easily here

Maybe JSX tools just needs some re thinking to get the same SFC experience

Re: Next.js 12

#137

Post by Rauchg »

CGamesPlay wrote: post #83

I don't want to hate on Next, because I do like using the framework, but a new major version every 5 months for the lifetime of the project? How does anybody actually develop an application when you have to spend so much time keeping your framework up to date?

Stories like this[1] are not uncommon:

> One of our users upgraded from Next.js 2.0-beta to 11 in 5 minutes.

> As @timneutkens said in the Q&A, Next.js incrementally improving without breaking changes is worth the investment.

If this is not the case, please let us know. We try to be very careful around this, and always leave breadcrumbs for easy upgrades in the DX if we absolutely must change something to move the project forward.

[1] https://twitter.com/rauchg/status/1405241003653484546

Re: Next.js 12

#138

Post by jekude »

swyx wrote: post #119
jekude wrote: post #48

If Next.js + Vercel is the leader of the production-ready frontend-as-a-service space, why hasn't a similar leader emerged in the backend-as-a-service space? I would love a clean Vercel-like abstraction on top of standard cloud primitives (functions, queues, events, workflows, etc.) with everything wired up nicely and focused on developer experience. It just seems like AWS is so configuration heavy that it is ripe fo…

https://supabase.io has: - Postgres DB (+ admin panel + realtime sync + search + workflows) - Auth - Storage - Functions (beta) (disclosure: am small angel investor) its interesting that you consider workflows a "standard cloud primitive". what do you currently use? (i work on a workflow engine myself)

Current company's infrastructure is currently all on AWS, so using Step Functions. However I really _really_ like temporal.io's code-first solution (just didn't want to self-host).

Perhaps the dust on best practices / tech for workflows or sagas just hasn't settled yet to include in a framework like the one I am envisioning.

In general I think Supabase is fantastic in terms of the interoperability of all of the features they introduce. Just waiting on functions (and perhaps events / queues for async communication).

Re: Next.js 12

#139

Post by jekude »

Zababa wrote: post #120
jekude wrote: post #82

Earlier quoted context omitted.

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 al…

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

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.

Re: Next.js 12

#140

Post by GordonS »

no_wizard wrote: post #136

This is really amazing, is the end result here that they are ultimately opting out of webpack in favor of SWC? It also compiles modules and such. Will have to take a look at the underlying infrastructure here! Interestingly I think that’s the major win of SWC over esbuild: you get a Babel like plug-in ecosystem for AST transformations and such. Downside: there currently isn’t a way to run asynchronous transforms, muc…

Sorry, "SFC" and "SWC"?
Post reply on HN