Live data from Hacker News

Next.js 10

nextjs.org

201–206 of 206 posts

Re: Next.js 10

#201

Earlier quoted context omitted.

I had also avoided modern web up until very recently. I focused only on Django sites and wrote custom JavaScript as necessary. I even did a 3 month django project with a view that was almost entirely JavaScript—it would have been a perfect candidate for react but I refused. As a compromise with myself I used es6 js on that and eliminated use of jQuery from my code. About a month ago I started work on react. I had ver…

Thanks. I really appreciate the story. I'm a long time Django fan so your story resonates. Maybe I'll give React another try one of these days...

You’re welcome. I wish someone in my position was able to give me this same info a year ago.

The other thing I’d add is that on my “old” projects, my JS is way better now that I’ve practiced so much es6 in React.

Re: Next.js 10

#202
post #186
post #10

The big elephant in the room most of these frameworks are missing is partial hydration. Instead of hydrating the whole page, only the interactive parts are hydrated, sending the absolutely minimal JS needed to the client. AFAIK only Marko has this feature today. Since it's developed and used at Ebay they focused on the best SSR+hydration experience from the start. Imba v2 will also have patial hydration (confirmed by…

> only Marko has this feature not true, Elderjs from the Svelte ecosystem does exactly this

Does Elder do SSR or only SSG? It's sort of crazy how automatic partial hydration is in Marko. You just write your code and it works. No extra consideration etc.

Re: Next.js 10

#203
post #10

The big elephant in the room most of these frameworks are missing is partial hydration. Instead of hydrating the whole page, only the interactive parts are hydrated, sending the absolutely minimal JS needed to the client. AFAIK only Marko has this feature today. Since it's developed and used at Ebay they focused on the best SSR+hydration experience from the start. Imba v2 will also have patial hydration (confirmed by…

I remember thinking when I first saw Marko it's kinda crazy how unknown Marko is given how well they've been doing streaming SSR and Partial Hydration for years. At production scale at eBay.

Re: Next.js 10

#204
post #111
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.

Their response to "How do I test Svelte apps?"

"We don't have a good answer for that yet, but it is a priority."

I was interested in Svelte until I read this. When they have a good answer, I'll be interested again.

https://svelte.dev/faq#how-do-i-test-svelte-apps

Re: Next.js 10

#205

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…

Svelte is the lead of virtualdom less `ui=f(data)` language/framework. It's the only one you can mutation DOM without its program being corrupted (though not sure if you try hard, it could be)

There is only 1 thing that would make me switch from Elm to Svelte is template as a function. Make it compose like functions! So that you can have as many as functions you want. With current Svelte, these functions are bunch of files .. unfortunately.

Re: Next.js 10

#206
post #111

Earlier quoted context omitted.

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.

Their response to "How do I test Svelte apps?" "We don't have a good answer for that yet, but it is a priority." I was interested in Svelte until I read this. When they have a good answer, I'll be interested again. https://svelte.dev/faq#how-do-i-test-svelte-apps

The solution to this, I believe, is making template a function: https://news.ycombinator.com/item?id=25023551
Post reply on HN