Fresh – Next-gen web framework • Hacker News Board

Looks nice. A lot of ideas shared with remix but native to deno. Will def check it out when it’s production ready. Also, beautifully juicy hero animation.

Re: Fresh – Next-gen web framework

#6

Post by pcj-github » Mon, Jun 13, 2022, 2:31 AM UTC

Excited about this!

Docs should include obvious link to github repo: https://github.com/lucacasonato/fresh (edit: it's already in the footer)

Also, deno/x needs an update: https://deno.land/x/deno_fresh

Re: Fresh – Next-gen web framework

#7

Post by munchenphile » Mon, Jun 13, 2022, 2:34 AM UTC

edmcnulty101 wrote: post #2

What is hydrating the client?

> Island based client hydration for maximum interactivity.

This honestly reads like satire. It sounds like something on the sarcastic VanillaJS homepage.

This gibberish being the second bullet point in a list of core features is a huge turn off. I know it’s tongue in cheek, but still

Re: Fresh – Next-gen web framework

#8

Post by niix » Mon, Jun 13, 2022, 2:35 AM UTC

Ryan Dahl is at it again?

Re: Fresh – Next-gen web framework

#9

Post by lmiller1990 » Mon, Jun 13, 2022, 2:37 AM UTC

I 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?

Re: Fresh – Next-gen web framework

#10

Post by halfmatthalfcat » Mon, Jun 13, 2022, 2:39 AM UTC

Why use '$' as the package namespace prefix/identifier instead of the already agreed upon convention of '@'? E.g. '@fresh/{package}' vs '$fresh/{package}'.

Seems like a departure from the norm for no reason unless there's some Deno particularity about it.