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

Next.js 10

nextjs.org

Post reply on HN
Print view View original

111–120 of 206 posts

Re: Next.js 10

#111

Post by dfrsol »

erokar wrote: post #87
bamazizi wrote: post #71

I understand this is a Vercel framework and probably a great distribution channel for new business and increasing overall revenue. But, I'm a bit disappointed the "next" version is more about Vercel's own internal business agenda. Promoted as amazing "DX" is not really true. It had a better DX compared to the other tools, that's why it grew so popular, but not seeing anything real DX related in version "10". Other to…

I feel the same way. We've switched from React to Svelte at work. Going back to React would be a step backwards for us, so much feels needlessly overengineered with awkward APIs. React was a great improvement on Angular, but luckily things are still moving forward.

How are y'all testing your svelte apps/components? Jest+Testing Lib seems to have issues calculating code coverage and there are few quirks like having to do work arounds to test slots that prevent me from totally switching over.

Re: Next.js 10

#112

Post by bamazizi »

fasteo wrote: post #110
erokar wrote: post #87

Earlier quoted context omitted.

I feel the same way. We've switched from React to Svelte at work. Going back to React would be a step backwards for us, so much feels needlessly overengineered with awkward APIs. React was a great improvement on Angular, but luckily things are still moving forward.

Which UI component library, if any, do you use with Svelte ?

Technically any static ui library can easily be turned into reactive components in any of the frameworks. I personally use & recommend Tailwind css, you still need to design/build your UI elements and components but Tailwind helps you speed it up.

Re: Next.js 10

#113

Post by mindrun »

citruspi wrote: post #106
mindrun wrote: post #100

Earlier quoted context omitted.

Whenever the Next.js + Vercel combo gains a new feature, Vercel ensures that it's available in standalone Next.js too – even when deployed to other providers. That's true for all the features mentioned in the Next.js 10 blog post: Image optimization, Internationalization, but also Analytics. Since you mentioned the latter: Did you notice that we wrote a detailed documentation page about how to report those metrics to…

> Did you notice that we wrote a detailed documentation page about how to report those metrics to any service of your choice? Perhaps you should link that on the Analytics[0] page instead of directing users to contact the sales team for more information on non-Vercel deployments. [0] https://nextjs.org/analytics

Great suggestion! We'll add a link right after the conference.

Re: Next.js 10

#114

Post by dbbk »

jasode wrote: post #65
pbowyer wrote: post #40

> Nowadays users browse the web using their phones, tablets, and laptops, yet images are still as a one size fits all. For example: sites load a 2000 by 2000 pixel image, but phones are only displaying it as 100 by 100 pixels. That's what srcset & were invented for. > Furthermore, 30% of images on web pages are outside of the initial viewport, meaning the browser loads images that a user does not see until they scrol…

>That's what srcset & were invented for. I don't know Next.js but I just spot checked a comparison to see if srcset is an exact subtitute. - If I'm reading CanIUse chart correctly, it says IE11 isn't compatible.[1] - syntax of srcset requires manual and verbose specification of different source images. E.g. from MDN[2]: - Next.js example[3] is simpler and shorter: import Image from 'next/image' The Next.js post also…

Next's Image component renders out to the first example. They are ultimately the same thing.

Re: Next.js 10

#115

Post by Vinnl »

sandGorgon wrote: post #107

Nextjs has the dejavu vibe of docker. It is a brilliant framework dragged slowly and inexorably into "platform lock-in". Nextjs has defocused on SSR (which was the original selling point of a server side Reactjs). And all the other cool features only run on Vercel. It is getting next to impossible to deploy Nextjs (with all its features) on GAE for example...or heroku. There are other alternatives to Nextjs that are…

Doesn't it still come with a server that you can just run on Heroku? That's what I'm doing, and although I'm not at v10 yet, I can't recall any major challenges there.

Re: Next.js 10

#116

Post by acoard »

truesy wrote: post #45

I have mixed emotions on this framework. If you're doing a simple project, Next is the best around. Also great for marketing pages, etc. But if you have a more sophisticated app, with an API, page routes that need to toggle based on cookies, etc, then you have to integrate something like Express. I've done this several times with Next, and it just doesn't pay off. I've also tried to use it at work, but it changes rap…

Do you mind enumerating the specific pain points?

Routing seems like the biggest limitation, but it's a trade off to use their file-based routing which has it's pros too. This precludes page transitions unless you do some really ugly work arounds.

Re: Next.js 10

#117

Post by erokar »

dfrsol wrote: post #111
erokar wrote: post #87

Earlier quoted context omitted.

I feel the same way. We've switched from React to Svelte at work. Going back to React would be a step backwards for us, so much feels needlessly overengineered with awkward APIs. React was a great improvement on Angular, but luckily things are still moving forward.

How are y'all testing your svelte apps/components? Jest+Testing Lib seems to have issues calculating code coverage and there are few quirks like having to do work arounds to test slots that prevent me from totally switching over.

Our test coverage of the Svelte apps is meagre so far to be honest.

Re: Next.js 10

#118

Post by sophiebits »

mulholio wrote: post #58
pier25 wrote: post #21

Earlier quoted context omitted.

They've been talking about it for years alongside with SSR streaming. Nothing concrete so far.

I get the sense the React team don't really care about SSR as it's not a massive use case for FB.

The React team has been focusing much more on SSR lately. I think it's likely we'll see big things in 2021.

Re: Next.js 10

#119

Post by erokar »

fasteo wrote: post #110
erokar wrote: post #87

Earlier quoted context omitted.

I feel the same way. We've switched from React to Svelte at work. Going back to React would be a step backwards for us, so much feels needlessly overengineered with awkward APIs. React was a great improvement on Angular, but luckily things are still moving forward.

Which UI component library, if any, do you use with Svelte ?

UI component libraries for Svelte are a little lacking in maturity in my experience. I would recommend including a CSS library such as Bootstrap or Materialize. Tailwind is also popular, but not my cup of tea.

Re: Next.js 10

#120

Post by Xevi »

yawnxyz wrote: post #109
bamazizi wrote: post #71

I understand this is a Vercel framework and probably a great distribution channel for new business and increasing overall revenue. But, I'm a bit disappointed the "next" version is more about Vercel's own internal business agenda. Promoted as amazing "DX" is not really true. It had a better DX compared to the other tools, that's why it grew so popular, but not seeing anything real DX related in version "10". Other to…

I'm rewriting a bunch of my Vue components into Svelte, and turning my Nuxt (which were previously React/Next) projects into Sapper, and it's a crazy easy process. My Svelte codebase is tiny compared to my Vue codebase. I'm slightly "worried" about Sapper not being at v1.0 yet but... it's been working great for my MVPs

I'm pretty out of the loop when it comes to Svelte/Sapper. I've looked at it, but never used it. However I did recently spot that they're already working on a successor to Sapper called Svelte Kit. So maybe that's why Sapper isn't at 1.0, and maybe never will be.

https://github.com/sveltejs/sapper/issues/1429

Post reply on HN