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

Fresh – Next-gen web framework

fresh.deno.dev

Post reply on HN
Print view View original

31–40 of 463 posts

Re: Fresh – Next-gen web framework

#31

Post by jchw »

burlesona wrote: post #11

Quoted post unavailable.

That’s because it’s literally, not conventional templates. It is, from what I gather, Preact components, which can be rendered on the server and client isomorphically. The same component code runs on both sides. That’s not templates.

Re: Fresh – Next-gen web framework

#35

Post by rubenfiszel »

I both love it and hate it. Most of the features are similar to sveltekit/next.js. I get that the biggest benefit is the deno deploy integration for ssr on the edge. But I would have highly preferred a new flavor of sveltekit where deno deploy is a build adapter (like cloudflare workers currently are) and the script part of svelte could be set as "ts-deno". No need to reinvent the wheel yet again and split the ecosystem more.

Re: Fresh – Next-gen web framework

#36

Post by gavinray »

On the part about adding interactivity:

  > "To include this in a page component, one can just use the component normally. Fresh will take care of automatically mounting the island component on the client with the correct props:"
How does a developer know what rendering is going to take place client-side vs server-side, and is there any way to control this?

Or is it all fully "magical"

Re: Fresh – Next-gen web framework

#37

Post by jchw »

0des wrote: post #28

Quoted post unavailable.

Even if you wanna be cynical, this is a really boring and overplayed take in my opinion. Most frameworks are indeed kind of bloated for running useless hello world demos. Most C compilers give you some kilobytes of code that isn’t necessary for hello world either, even worse for other respected and modern languages like Rust and Go. It can be forgiven if you consider that most of these things are not tuned for optimal hello world.

Re: Fresh – Next-gen web framework

#38

Post by oreilles »

xrd wrote: post #13

Very 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.

Other than helping creating websites, this has almost nothing to do with SvelteKit. SvelteKit: - Requires configuration and build - Doesn't support partial hydration - Ship JS to the client by default - Can also be used as static site generator or SPA framework (no server side code)

Re: Fresh – Next-gen web framework

#39

Post by smoochy »

miguel-muniz wrote: post #14
edmcnulty101 wrote: post #2

What 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 https://en.wikipedia.org/wiki/Hydration_(web_development)

No post body was provided.

Re: Fresh – Next-gen web framework

#40

Post by 0des »

Petersipoi wrote: post #33
niix wrote: post #8

Ryan Dahl is at it again?

From what I can tell, Ryan Dahl doesn't have anything to do with this (other than it using Deno). At the very least, he isn't a contributer to the Repo.

Deno is repeating a lot of the same things from node, but its in typescript now, and there's some rust involved, so that makes it good. Wait till you're this deep into your career and people are still hammering square pegs into the same well worn circle holes and you'll be the same way.
Post reply on HN