No post body was provided.
Fresh – Next-gen web framework
11–20 of 463 posts
Re: Fresh – Next-gen web framework
#12Ooh, some competition for Next.js?
Vercel is doing a really good job with Next, but it's good to see some competition. Of course, that means there's now 65,535 + 1 more way of serving a web page using Javascript (sigh).
Rehydration is a really big deal. Sounds dorky but it dramatically speeds up load times and such by serving flat HTML and injecting JS afterward, like the old days, except you can write code like it's not the old days.
Re: Fresh – Next-gen web framework
#13Very similar to sveltekit as well. I hope in the future you can swap out the preact for svelte.
The deno runtime is very interesting.
Most intriguing: no build step. That's a big difference from sveltekit which takes very readable input files and produces hardly readable files.
Re: Fresh – Next-gen web framework
#14What is hydrating the client?
Hydration is a technique where the content is rendered server side then client side JS attaches the necessary event handlers to make the UI interactive
Re: Fresh – Next-gen web framework
#15No post body was provided.
Re: Fresh – Next-gen web framework
#16Hmm. I don't see enough of an advantage over Next.js to make the leap, but good to see some innovation in this area.
Re: Fresh – Next-gen web framework
#17I don't fully understand the difference between this (and something like Remix, which seems similar) and other frameworks like Next.js (React) and Nuxt.js (Vue). Can someone explain a bit about the differences, and pros/cons to each?
Deno vs Node appears to be one of them.
Re: Fresh – Next-gen web framework
#18Quoted post unavailable.
Early PHP and Ruby frameworks don't provide anything to help you write client side interactive code, so you are on your own there, and you have to bring your own tools to do this.
Re: Fresh – Next-gen web framework
#19"Island based client hydration"
Is this ling that I'm missing? Or a lark?
Re: Fresh – Next-gen web framework
#20[deleted]