How do these companies make money offering so much for free?
Their enterprise version is super expensive, their integration with Amazon can give you an idea of their enterprise pricing https://aws.amazon.com/marketplace/pp/prodview-lwqascgzju3bo
Next.js 14
41–50 of 157 posts
Re: Next.js 14
#42How do these companies make money offering so much for free?
Vercel makes most of its revenue through its PaaS platform - which supports NextJS first-class, and is their recommend solution for hosting NextJS apps.
Re: Next.js 14
#43I think I'll be taking a step back from React/Next.js for the foreseeable future. I feel fortunate in that, for most of my projects, I can make architectural decisions such as this. Things took a turn with hooks (I have a feeling that's the general consensus, too). The nail in the coffin (at least for me) was React Server Components.
I gotta admit that its been liberating working outside the javascript/react realm. Using Go + HTMX + [insert tool here] has been a fairly easy transition. Is it a 1:1 replacement? No. Does it solve most of my use cases whilst providing a better developer experience? Absolutely.
I'm not trying to hate on React here. I just think its time to stop and ask ourselves "is this REALLY the best idea/tool for xyz?".
Re: Next.js 14
#44I'm confused by next.js, and previously considered vercel to be an AWS wrapper with a nicely styled website and some high level APIs over AWS. Any opinions someone could provide about what the value prop of these libraries/companies are? I dont see many real technology companies running these stacks, more so barely funded startups
React is a pretty narrow framework. It focuses on the components and doesn't really dictate how your app should be structured, which is part of why it's been successful: you can adopt it gradually and replace pieces of an existing app with it, until eventually your whole app is React.
Next.js is a framework built on top of React. It has a more defined structure for things like routing, and it provides useful tools for server-side rendering. It is definitely used in production by major companies and not just by "barely funded startups."
Vercel makes Next, among other popular JS and serverless offerings, and they offer various managed hosting services. I don't use Vercel's paid offerings, but they strike me as operating in the Heroku space, where they make it easy to get a simple app off the ground.
Re: Next.js 14
#45I missed this: https://vercel.com/changelog/vercel-postgres-is-now-availabl...
FWIW, “Vercel Postgres” is a white-label of Neon: https://neon.tech/blog/neon-postgres-on-vercel
Correct. Same price and limits. It’s just making integrating it into Vercel. So you can get Postgres/Redis/object storage and more with your frontend, in one bill.
Re: Next.js 14
#46Wait wtf, I clearly remember 13 came out of beta 4-5 months back. At this rate Next.js will be on version 20 by the end of next year.
13 came out in Oct 2022. https://nextjs.org/blog/next-13 PS: I’m not sure why hyperfurism’s reply was downvoted to oblivion. They were correct.
[deleted]
Re: Next.js 14
#47Fuck next.js. Honestly. Check out how it bundles and sends the entire react-dom library twice to every user on every page view https://github.com/vercel/next.js/issues/51508 . Fuck 1MB of JS to render a static HTML page. Fuck the image component, and not being able to optimise your image unless you use their cloud service for no reason at all. Fuck spending 3 hours working out why you’re not able to use relative imag…
Can we get a fuck for these automatic "stale" issue locking bots too? Ridiculous.
Re: Next.js 14
#48Looking at this i am so happy that i am still using my own component framework. In combination with a nice bundler like parceljs only 100kb for an entire frontend application. Less than 10ms to render a webapp. No trillions of layers. Just a page/render engine and small components like panels, buttons etc.
Why would you need all these fancy provided by next and other frameworks? In the end you constantly face limitations and performance issues.
Re: Next.js 14
#49Can you set a cookie from server component now?
You can set cookies in Server Actions or Route Handlers.
Re: Next.js 14
#50Server actions sounds great for small projects. Type safety in those calls seems like it can replace a tRPC server in small projects and SaaS MVPs.
Yeah, best part for me is end to end type safety across the server and client. tRPC really led the way here.