Earlier quoted context omitted.
Typescript is a real pain, I’m still trying to figure out why it’s so popular. The constant nagging and extra typing (no pun intended) when using it vs regular JavaScript makes it a pain. Then, there’s the extra parsing step to change it back to JavaScript. Idk I don’t see the value yet. Edit: I say “parsing step “ because that’s what it is. There’s no “compiling” and “transpile” is just a ridiculous way of saying pa…
Are you against typescript or types in general?
Why I'm using Next.js
61–70 of 86 posts
Re: Why I'm using Next.js
#62Is 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
After using TypeScript, I’m never going back to vanilla JavaScript if I can help it.
Re: Why I'm using Next.js
#63Is 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
After using TypeScript, I’m never going back to vanilla JavaScript if I can help it.
Re: Why I'm using Next.js
#64What are better options out there (for a Node developer) if you're not using Next.js? Going to rails isn't really an option I guess
I’ve been learning more of these stacks and found out about remix here in the nextjs release 14 thread. Remix seems pretty ok so far but I don’t have super strong feelings on nextjs either, it seems to work for me. I’m functioning as a system liaison at work for a team on nextjs which was my first exposure to it. That got my interest so I’ve been exploring front end frameworks lately. I would give remix a shot.
Re: Why I'm using Next.js
#65Earlier quoted context omitted.
The original article was written by a guy who had a founding responsibility for a rival framework. Pot, kettle?
So both read like ads then. What is your point? Why are you rushing on every comment critical of vercel?, I'm assuming you also work for them or you have been sponsored or taken money by them in their marketing department. Judging from their latest release of Next.js, nothing has really changed or been done (except v0 which is cool which is besides the point from Next). But the fact that I don't see an explicit discl…
Re: Why I'm using Next.js
#66What are better options out there (for a Node developer) if you're not using Next.js? Going to rails isn't really an option I guess
Are you being ironic? If not: Rails is most certainly an option, if building web stuff is your goal. I think it's lame how bad the documentation around it is 40 years in, which I can kind of forgive because of how well thought out and complete pretty much everything is, once you figure it out. That is not to say that there aren't very sensible JS options – for example AdonisJS is well long running, constructed and fe…
Re: Why I'm using Next.js
#67Earlier quoted context omitted.
The original article was written by a guy who had a founding responsibility for a rival framework. Pot, kettle?
So both read like ads then. What is your point? Why are you rushing on every comment critical of vercel?, I'm assuming you also work for them or you have been sponsored or taken money by them in their marketing department. Judging from their latest release of Next.js, nothing has really changed or been done (except v0 which is cool which is besides the point from Next). But the fact that I don't see an explicit discl…
In the post:
> I'm Lee. I work on Next.js.
On the homepage:
> I lead the community for Next.js
Re: Why I'm using Next.js
#68Earlier quoted context omitted.
Next’s support outside of Vercel is best effort it seems. Which is fine as Vercel funds it, but it feels like there is a conflict of interest. There is after all a reason for OpenNext’s existence.
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…
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 how to support Next features that require very tight cooperation from CDN/distributed cache magicks.
The total product is good, the web presence team is happy with Next and Vercel, I’m liking RSC and server actions, but I wanted to share my experience that beyond modest scale running Next yourself needs a lot of effort.
Re: Why I'm using Next.js
#69Earlier quoted context omitted.
So both read like ads then. What is your point? Why are you rushing on every comment critical of vercel?, I'm assuming you also work for them or you have been sponsored or taken money by them in their marketing department. Judging from their latest release of Next.js, nothing has really changed or been done (except v0 which is cool which is besides the point from Next). But the fact that I don't see an explicit discl…
> I don't see an explicit disclaimer here In the post: > I'm Lee. I work on Next.js. On the homepage: > I lead the community for Next.js
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.
Re: Why I'm using Next.js
#70Earlier quoted context omitted.
> I don't see an explicit disclaimer here In the post: > I'm Lee. I work on Next.js. On the homepage: > I lead the community for Next.js
> 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.