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

141–150 of 293 posts

Re: Next.js 12

#141

Post by nightpool »

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…

I find that React + styled-components in the same file gives me almost entirely the same experience as SFC.

Re: Next.js 12

#142

Post by DaiPlusPlus »

GordonS wrote: post #140
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"?

At least it isn’t SWF…

Re: Next.js 12

#143

Post by swyx »

jekude wrote: post #138
swyx wrote: post #119

Earlier quoted context omitted.

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

ah nice! make sure to fill out our waitlist if you want our managed service: https://temporal.io/cloud

meanwhile if you like workflows as code and want to stay in the AWS world what about AWS SWF? our CEO used to be tech lead of that and it shares similar ideas.

yeah we are hoping to establish what best practice/architecture for workflows looks like. Feedback/questions welcome: https://docs.temporal.io/blog/workflow-engine-principles

Re: Next.js 12

#144

Post by techpression »

leerob wrote: post #2

Hey everyone, Lee from Vercel here! Happy to answer any questions about Next.js 12. Personally, I'm extremely excited for the new Rust compiler.

Any chance we’ll get a proper official routing mechanic that doesn’t rely on the file system and magical file names?

Re: Next.js 12

#145

Post by chrisco255 »

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.

Right, they don't host the databases, but they do integrate with other database, etc. providers: https://vercel.com/integrations

Vercel itself I believe runs on a combination of Google Cloud and AWS.

Re: Next.js 12

#146

Post by simlevesque »

GordonS wrote: post #140
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"?

SWC, a typescript/js compiler: https://swc.rs/

SFC, single file components.

Re: Next.js 12

#147

Post by [deleted] »

OzzyB wrote: post #30
capableweb wrote: post #3

Nice, a completely new attack-vector: https://nextjs.org/blog/next-12#url-imports Documentation still not there, so can't check if they actually compare any checksums or anything. They also introduce their own `next.lock` which supposedly new tooling have to built around as well. Versioning management? What, we don't need that for where we're going. Finally it's fun to see it ending with: > We set out to build a zero…

> url imports Aren't they just taking a feather out of Golang's hat?

[deleted]

Re: Next.js 12

#148

Post by swyx »

melony wrote: post #65
mritchie712 wrote: post #56

Earlier quoted context omitted.

Supabase is headed in that direction and already works for most simple CRUD like apps.

Supabase is overly SQL heavy.

can you elaborate on what "overly SQL heavy" even means? it's just a postgres db as a service, use as much or as little as you want

Re: Next.js 12

#150

Post by throw123123123 »

Rauchg wrote: post #137
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 pr…

I've done at least 20 upgrades (user since next 1.0) and it is getting easier and easier to migrate.
Post reply on HN