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

51–60 of 106 posts

Re: Next.js 13

#51

Post by latchkey »

lghh wrote: post #45
latchkey wrote: post #10

// "alt" is now required for improved accessibility I'm all for accessibility, but let us decide when to implement it.

I'd rather spend a literal 6-character burden (alt="") to put an empty string in my little hobby projects than live in a world where non-hobby projects can skip adding alt. It should be very clear by just looking around on the internet that, when given the choice, accessibility will take a back seat.

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

Re: Next.js 13

#52

Post by latchkey »

cramforce wrote: post #31
latchkey wrote: post #26

Earlier quoted context omitted.

That's like the difference between null and undefined.

If you have no alt attribute, then screen readers read the URL! Empty strings are the way to go for decorative images

What if I have an app that no screen reader will ever read?

Re: Next.js 13

#53

Post by apozem »

AlmostAnyone wrote: post #14
nightski wrote: post #9

Earlier quoted context omitted.

Sigh another one? I thought Vite was the new thing.

Sigh? I think the speed improvement is awesome .

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.

Re: Next.js 13

#54

Post by rektide »

> With Server Components and nested layouts in Next.js, you're able instantly render parts of the page that do not specifically require data, and show a loading state for parts of the page that are fetching data. With this approach, the user does not have to wait for the entire page to load before they can start interacting with it.

Crazy huge user win.

I am a little nervous how much stuff Next does in the middle, how thoroughly it links front & back end. Streaming a page with chunks missing then streaming sections as they resolve is pretty advanced magic. Amazing DX experience but I also can think back to asp.net & remember huge viewstate blobs & utterly magic middle-layers, and those were powerful too, but impregnible bizarre systems to the developer & that wasnt good.

Next keeps hitting reaply really nice sweet spots & consolidates & tackles so many problems, and my trepidation is small at this point, but this is really redefining the page a lot, & I feel like I really want some deep dives on the technics involved here, want to know the magic is somewhat accessible & coherent, for fellow would be meddlers.

Re: Next.js 13

#55

Post by [deleted] »

lghh wrote: post #47
latchkey wrote: post #29

Earlier quoted context omitted.

Which is ok too. It is far better than encouraging people to write alt="" or alt="asdf". See also (naming things): https://twitter.com/secretGeek/status/7269997868

They are encouraging people to write alt text, not encouraging people to write alt="". That's like saying "Typescript just encourages people to make everything `any` instead of defining types. It's a useless addition over JS." Sure, you _could_, but most actually use the actual tool.

[deleted]

Re: Next.js 13

#56

Post by abujazar »

cramforce wrote: post #31
latchkey wrote: post #26

Earlier quoted context omitted.

That's like the difference between null and undefined.

If you have no alt attribute, then screen readers read the URL! Empty strings are the way to go for decorative images

Alt is a required attribute of the tag, so requiring it is just basic validation. C code won't compile if you omit the semicolon after statements, either.

Re: Next.js 13

#57

Post by Vinnl »

nthitz wrote: post #36
slooonz wrote: post #33

I find the data fetching example extremely confusing… 1. Where does this "use" comes from ? It is not present in the official React API reference : https://reactjs.org/docs/react-api.html 2. It says that the value is not serialized, but what if Page is rendered client side and I want getData to always be executed server side (for example, it may contains secret API key, or make a database call) ? 3. getData is async,…

it's a new "hook", https://vived.io/new-hook-is-coming-to-react-frontend-weekly... https://github.com/reactjs/rfcs/pull/229 contain some discussion

But `use` is still just in the RFC phase, right? How can Next.js already be (committing to) using it?

Re: Next.js 13

#59

Post by latchkey »

joshribakoff wrote: post #58
latchkey wrote: post #10

// "alt" is now required for improved accessibility I'm all for accessibility, but let us decide when to implement it.

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.

Re: Next.js 13

#60

Post by chrisco255 »

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.

It's a bigger ecosystem than all others, and there's no batteries included in web development, so it necessitates the need for tooling to be built from scratch.
Post reply on HN