*opens random website*

*Thinks for the 578th time* how the fuck is thjs website so blazing fast?!? Let me guess ITS BUILT IN NEXTJS RIGHT?

*Open view page source* and surely enough i see _next code in it

God fucking damn it. Is the future of web nextjs?

Very rarely see react. Rarely see angular. And i never see vue. Nextjs is all over the fucking place

vue3 is common though
idk about fast or not coz usually the bottleneck is the network calls and not the client-side JS

Do you have an example link of such a website?

https://krausest.github.com.io/js-f...

might be interesting in that context.
It's basically benchmarks of a default set of tests implemented in a whole bunch of frameworks, to see, what performs best.

You'll notice that react is consistently somewhere in the back of the table

the future of the web is still WASM.

You should not wonder how nextjs is fast. You should wonder how the other crap is so slow.

Though, next.js uses react but much of it server side.

This works since we have fast internet and by caching anything that is not personalized much of it is more or less loading of static pages which is fast.

Du in the end its still mostly the developers of the site, do they prioritize performance or is it all visuals and features?

@thebiochemic your link is a bit "fucked up" the working link is
https://krausest.github.io/js-frame...

without .com

@j0n4s yeah thanks, no idea, how that got in there..

@tosensei I wonder what will be adopted first. WASM or IPv6?

@lungdart WASM is already in production lol. You can even write .Net apps in it. IPV6 will always be limited to cell networks.

@AlgoRythm IPv6 adoption is more prevalent than wasm.

https://google.com/intl/en/...

@lungdart 97% of currently used browsers support WASM. I believe that’s larger than IPV6.

Just because not all websites choose to be written in WASM doesn’t mean it’s not extremely widely adopted

@AlgoRythm 100% of AS numbers support ipv6. Just because the networks don't purchase ipv6 doesn't mean it's not widely supported.

@lungdart there’s a higher % of legacy systems that cannot / will not adopt IPV6 compared to the % of consumer devices/browsers that cannot/ will not support WASM and that will be true for at least 25 more years

@AlgoRythm not at the network level.

Ipv6 has been fully supported for 15 to 20 years by switches and routers. Some non carrier grade appliances were slower to pick up support (waf, ids, packet capture/scrubbing) but that's been solved for the last 5 to 10 years.

@lungdart yes but if that were the only roadblock to ipv6 we would already have widespread adoption by now rather than high-40% at best. Unfortunately there’s other things in the way that have stopped adoption including ISPs being greedy geeks about it (why would they speed up adoption when they’re the ones selling the precious IPv4 addresses?)

This leads to even modern countries such as Spain having less than 1% adoption, and as IPv6 adoption increases, the need for it decreases in a catch 22. Because the ipv4 address pool becomes less and less exhausted, there’s less pressure for older systems to go through the network architecture upgrade required.

All this to say that the road to WASM is a lot shorter and smoother. Since 95% of browsers are chromium anyways, the only upgrade step was to update whatever you’re using. Usually this is done completely transparently to the user.