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

Next.js 13

nextjs.org

Post reply on HN
Print view View original

71–80 of 106 posts

Re: Next.js 13

#71

Post by jokethrowaway »

parhamn wrote: post #20

The next-gen bundler rewrites are getting insane, just as things were consolidating in the other parts of JS. We now have: - EsBuild - SWC (also written by someone who works at Vercel) - TurboPack - Vite (rollup) - Parcel - Rome I've noticed in the javascript ecosystem there is much less convergence than in other languages. Everyone wants a flag in the ground.

everyone believes they can write some JS and call themselves developer

bigger audience, bigger chance to make it big selling crap to developers so more personalities try to build an audience by making OSS

Re: Next.js 13

#72

Post by googlryas »

abujazar wrote: post #49
googlryas wrote: post #27

Earlier quoted context omitted.

Which just means codebases will be littered with alt="" for no reason.

It's often better to specify alt="" than not at all, because screen readers may use the filename instead if there's no alt attribute.

That's actually a detriment then, if the "fix" for no a11y makes screen readers think they should use no alt text, instead of some possibly meaningful alternate.

Re: Next.js 13

#73

Post by AlmostAnyone »

nightski wrote: post #64
apozem wrote: post #53

Earlier quoted context omitted.

I'm quite alright with new tooling every six months when the new thing is orders of magnitude faster. If people want to compete to make my job as a frontend dev easier and faster, that is just fine .

Ideally we could learn how to make the existing tools better/faster and create software that can evolve rather than re-writing everything from scratch every six months.

There was many years before people started trying to replace Webpack.

Re: Next.js 13

#74

Post by lghh »

randomguy0 wrote: post #66
latchkey wrote: post #51

Earlier quoted context omitted.

I'm curious why you think that forcing people to write alt="" is going to improve accessibility?

Because that’s how screen readers know the image is decorative. It literally is/improves accessibility.

Additionally, the developer is more likely to actually write alt text when it's not decorative.

Re: Next.js 13

#75

Post by [deleted] »

halfmatthalfcat wrote: post #65
nightski wrote: post #25

Earlier quoted context omitted.

Actually it tells me that the javascript ecosystem fails to build software that can adapt to change. The culture is to throw everything out and start fresh every time they want to do something different. It's terrible engineering.

Thankfully that's just your opinion. I appreciate all the innovation and experimentation that's happening. Nobody is dictating you or anyone else use these tools.

[deleted]

Re: Next.js 13

#76

Post by nightski »

AlmostAnyone wrote: post #73
nightski wrote: post #64

Earlier quoted context omitted.

Ideally we could learn how to make the existing tools better/faster and create software that can evolve rather than re-writing everything from scratch every six months.

There was many years before people started trying to replace Webpack.

True but webpack itself had a ton of churn and made practically no effort to maintain backwards compatibility causing a ton of work with each major update.

Re: Next.js 13

#77

Post by nightski »

halfmatthalfcat wrote: post #65
nightski wrote: post #25

Earlier quoted context omitted.

Actually it tells me that the javascript ecosystem fails to build software that can adapt to change. The culture is to throw everything out and start fresh every time they want to do something different. It's terrible engineering.

Thankfully that's just your opinion. I appreciate all the innovation and experimentation that's happening. Nobody is dictating you or anyone else use these tools.

My opinion based on decades of experience in web development. I've been through this churn dozens of times, it is tiring. The other ecosystems I work with do not work this way and yet they still innovate a lot.

Re: Next.js 13

#78

Post by elforce002 »

I started my journey with Vue, then Nuxt (of course),then switched to React and last year started to use Nextjs. So far I have no complains (at least no big ones).

With new frameworks poping out (qwik, remix, fresh, etc...), it's getting really interesting and tiresome at the same time.

We're migrating all our platforms to React/Next and we couldn't be happier. Is it perfect? Nothing really is. Next is good enough, the community is engaged, the ecosystem is big, and the industry is basically dominated by react (giving react devs some sort of peace of mind when looking or switching jobs).

Sometimes, you have to pick a piece of tech and roll with it as long as the tech keeps improving and the community improves alongside it. Nextjs is currently doing it.

Re: Next.js 13

#79

Post by dariusj18 »

latchkey wrote: post #59
joshribakoff wrote: post #58

Earlier quoted context omitted.

The HTML spec says it is required, even if you don’t think it should be required it is. https://html.spec.whatwg.org/multipage/images.html#alt

NextJS could just create alt="" when rendering the HTML element from their element.

I think the compromise would be an optional build parameter that allows this functionality.

Re: Next.js 13

#80

Post by AlmostAnyone »

nightski wrote: post #76
AlmostAnyone wrote: post #73

Earlier quoted context omitted.

There was many years before people started trying to replace Webpack.

True but webpack itself had a ton of churn and made practically no effort to maintain backwards compatibility causing a ton of work with each major update.

Hmm, I am using it since v2 and I disagree, it was not so bad. I saw a lot of people had overcomplicated configs that could be simplified a lot, I guess those had some problems upgrading... But mine never had much problems (and not just because my needs were simple...), I just removed some options when going to v4 and that's about it.
Post reply on HN