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

Next.js 14

nextjs.org

Post reply on HN
Print view View original

151–157 of 157 posts

Re: Next.js 14

#151

Post by nvm0n2 »

leerob wrote: post #65
cphoover wrote: post #33

One weird issue I had with next 13 was radio button groups did not work. The suggested fix from a core next contributor and fb employee was to "Upgrade to a canary release"... I get that you are building all these new cool features, but that cannot put basic functionality and backwards compatibility at risk. Radio buttons have been around forever, I'd assume that they are being used by tons of websites all ove the pl…

The reason we suggest upgrading is because it’s extremely common that issues are already fixed or they cannot reproduce when we ask them to upgrade. It helps with issue triage so we can properly prioritize and fix issues. If you can link the issue with a reproduction, I’m happy to look into it.

Generally, the expectation is that developers know what bugs have been fixed or can quickly check, so users aren't expected to just constantly retry on whatever today's HEAD is. That takes a lot of their time, and you already know what changes you're making so should be able to determine quickly if a bug was fixed.

Re: Next.js 14

#152

Post by 10xDev »

satvikpendem wrote: post #144
10xDev wrote: post #60

Earlier quoted context omitted.

Notice how you subconsciously called Next a product.

How is it not a product? It is produced and used. Many types of software are also products, whether they're VC funded or not.

I am not arguing that it is not. I very much agree Next is a product because it very much fits its definition: "an article or substance that is manufactured or refined for sale.".

But this is wrong by definition: "Many types of software are also products, whether they're VC funded or not."

Re: Next.js 14

#153

Post by cockatiel_day »

leerob wrote: post #136
cockatiel_day wrote: post #135

My ongoing concern with Next is the Vercel's team unresponsiveness to page-breaking bugs coming off of features marked "stable" and in the docs. Lately, it seems like most issues aren't even being acknowledged. It's pretty frustrating to encounter a bug in a documented use case, spend hours trying to fix it, realize it's a Next issue that was filed months ago but has yet to receive a response from Vercel, or to have…

I'm sorry that we haven't been able to respond fast enough. Hundreds of issues are opened every month, and the rate is increasing. We're working hard to try and triage as best as possible and hopefully hiring more folks to help out as well, too. Could you share the issues you're running into? While there's going to continue to be bugs and things to improve in the framework (it will never be "perfect" or "done"), that…

I'll add, it's kind of baffling to hear that things are stable, there are just ton of issues you can't get to.

I'd posit that Next has a ton of users, and a ton of issues, because it prematurely marks features as stable, and then markets them aggressively. Instead of working through these issues in beta with a manageable number of early adopters with aligned expectations, Next gets more than they can handle, frustrated that features sold as production ready are not. This, to me, is a questionable business strategy, not a sound technical one.

Re: Next.js 14

#154

Post by maowtm »

BoorishBears wrote: post #137
cyral wrote: post #107

Earlier quoted context omitted.

Your comment sounded like you expected NextJS to add "use client" to everything to prevent it from breaking, I misunderstood, which is what my comment was referring to. I see that you mean they funded this effort that results in other libraries breaking. You may want to consider using more precise language instead of questioning others intelligence, it really isn't necessary.

I questioned if you understood the topic of my comment, and you replied that you misunderstood the topic. Jumping from that to somehow being an attack on your intelligence is ridiculous. Also not sure how much more precise I can be in saying "they funded this effort" than my original comment which says "Vercel managed to fund an effort"

> Didn't realize I needed to put this together for you,

Re: Next.js 14

#156

Post by wavo »

andrasbacsai wrote: post #130

Why don't people use Laravel/Rails/Django and make good web apps in no time? So much pain could fly away instantly.

i guess 'possibly' the holy grail could be the laraval/rails/django mental model of serving routing and page behavior from the bandend, however using the same language for back as front and having things linked up in a typesafe way. wouldnt be perfect for every situation but would have a good mental model when youre developing a web app type of product where there's little distinction between front and back and theres only one client in mind for consuming server behavior.

Re: Next.js 14

#157

Post by kugelblitz »

wavo wrote: post #156
andrasbacsai wrote: post #130

Why don't people use Laravel/Rails/Django and make good web apps in no time? So much pain could fly away instantly.

i guess 'possibly' the holy grail could be the laraval/rails/django mental model of serving routing and page behavior from the bandend, however using the same language for back as front and having things linked up in a typesafe way. wouldnt be perfect for every situation but would have a good mental model when youre developing a web app type of product where there's little distinction between front and back and there…

Now with htmx, you can actually just generate the html in the backend and send the fully formed stuff to the frontend. No need to JSON-Api-fy everything first, then de-jsonify again in the frontend.
Post reply on HN