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

Why I'm using Next.js

leerob.io

Post reply on HN
Print view View original

71–80 of 86 posts

Re: Why I'm using Next.js

#71

Post by colesantiago »

leerob wrote: post #70
colesantiago wrote: post #69

Earlier quoted context omitted.

> I don't see a 'DISCLAIMER: I WORK AT VERCEL' at the top on here... I still don't see this anywhere at the top of your website and not deceptively hidden and buried on your website. Also: > I'm Lee. I work on Next.js. > I lead the community for Next.js Isn't explicit, there are a few open source contributors who work on Next.js but don't work at Vercel. So my point still stands on this being an ad for Vercel.

The next sentence in the posts says that I work at Vercel. Grasping for straws.

I'm not the only one calling this deceptive non disclaimer practice out:

https://news.ycombinator.com/item?id=38048313

https://news.ycombinator.com/item?id=38048847

Re: Why I'm using Next.js

#72

Post by hu3 »

leerob wrote: post #54
buf wrote: post #3

Pretty sure you use it because vercel likes the frontend engineers who don't know how/or care to deal with the backend.

There's a lot of misunderstanding of what "frontend" and "backend" are: https://www.industrialempathy.com/posts/frontend-backend/

Perhaps with desktop apps or low level systems it can get confusing but for traditional web the definition is usually:

If it runs in the browser, it's frontend. Server? Backend.

There's SSR but the name itself clarifies: Server Side Rendering.

Re: Why I'm using Next.js

#73

Post by lwhi »

hu3 wrote: post #49
lwhi wrote: post #33

Earlier quoted context omitted.

[flagged]

It's good practice to introduce strong biases at the top of articles so readers can take that into consideration right away. The article they are responding to did precisely that on their second paragraph: > I’ve been using Remix since it was first released in 2020. I loved it so much I joined the team for 10 months to help get the community going and now I recommend and teach Remix on EpicWeb.dev. [1] [1] https://ww…

He _does_ introduce the fact at the top of the article!

This feels very much like a targeted attack.

Re: Why I'm using Next.js

#74

Post by lwhi »

colesantiago wrote: post #71
leerob wrote: post #70

Earlier quoted context omitted.

The next sentence in the posts says that I work at Vercel. Grasping for straws.

I'm not the only one calling this deceptive non disclaimer practice out: https://news.ycombinator.com/item?id=38048313 https://news.ycombinator.com/item?id=38048847

This feels like a witch hunt. Totally unacceptable.

Re: Why I'm using Next.js

#75

Post by ushakov »

jitl wrote: post #68
Tehnix wrote: post #29

Earlier quoted context omitted.

I really don’t understand this sentiment, it is extremely easy to build and deploy Next.js yourself?? You either: - Build static files and host it like any other framework (e.g. throw it in an S3 bucket)[0] - Or, run a Node.js server Where’s the Vercel exclusive part there? [0] Here’s me doing exactly that, going through the same steps I would for literally any Frontend framework, including the WASM alternative I als…

I helped stand up Notion’s marketing site ( https://notion.so/product ) on NextJS. It’s really annoying / impossible to implement all the fancy caching, incremental revalidation, etc if you need to run more than one instance to serve the load you get. Or you need a horrendously complex AWS buzzword graph that will kinda sorta do the things. We switched from AWS ECS deployment to Vercel after tiring of figuring out ho…

Curious whether you considered any other frameworks?

Re: Why I'm using Next.js

#76

Post by colesantiago »

lwhi wrote: post #74
colesantiago wrote: post #71

Earlier quoted context omitted.

I'm not the only one calling this deceptive non disclaimer practice out: https://news.ycombinator.com/item?id=38048313 https://news.ycombinator.com/item?id=38048847

This feels like a witch hunt. Totally unacceptable.

How is pointing out an advertisement and asking for an explicit disclaimer at the very top of a marketing blog post a witch hunt?

Re: Why I'm using Next.js

#77

Post by gnabgib »

pier25 wrote: post #36

This seems to be a response to this other one titled "Why I won't use Nextjs" https://news.ycombinator.com/item?id=38018217

Seems to be? That's declared on the first line of the article. An attempt to balance sentiment on the web, perhaps.

Re: Why I'm using Next.js

#78

Post by jitl »

ushakov wrote: post #75
jitl wrote: post #68

Earlier quoted context omitted.

I helped stand up Notion’s marketing site ( https://notion.so/product ) on NextJS. It’s really annoying / impossible to implement all the fancy caching, incremental revalidation, etc if you need to run more than one instance to serve the load you get. Or you need a horrendously complex AWS buzzword graph that will kinda sorta do the things. We switched from AWS ECS deployment to Vercel after tiring of figuring out ho…

Curious whether you considered any other frameworks?

Site predates Astro, Remix, etc. There was some interest in Gatsby but I said no (seems horribly over engineered, adds GraphQL for no good reason, like storybook promises a lot but seems to leave the team doing extreme amount of npm upgrade work).

I think Next was the clear winner, we knew what we were getting into with hosting it to some degree and it was still worth because of how well it fits the team.

Re: Why I'm using Next.js

#79

Post by BigJono »

lovetocode wrote: post #34

Is anyone just using vanilla React with no TypeScript or Framework of any kind? I’ve tried Remix and Next js and just find them so cumbersome. Typescript causes me more headaches

Yes, I am, all the best devs I know are, and I honestly believe it's the 10x play right now.

Since 2016 I've seen reasonably large enterprise SaaS projects with similar scopes go from $5M builds to $50M builds without anyone else batting an eyelid. I have no idea what's going on in the industry at the moment.

React, Express, node-postgres. It worked 7 years ago. It works now. I can't even remember the last time I got stuck implementing any kind of business requirement with that very basic stack. Compare that to my day-to-day in 2023 where I'm spending hours every day fucking around with old stack overflow posts and shitty documentation trying to get TS/Next/Gatsby/NestJS or whatever else working.

Re: Why I'm using Next.js

#80

Post by pier25 »

gnabgib wrote: post #77
pier25 wrote: post #36

This seems to be a response to this other one titled "Why I won't use Nextjs" https://news.ycombinator.com/item?id=38018217

Seems to be? That's declared on the first line of the article. An attempt to balance sentiment on the web, perhaps.

Thanks I obviously didn't read the marketing piece.
Post reply on HN