Live data from Hacker News

Fresh – Next-gen web framework

fresh.deno.dev

91–100 of 463 posts

Re: Fresh – Next-gen web framework

#91
post #79
post #71

Earlier quoted context omitted.

This is the same thing I dislike about NextJS. What is the argument for using the filesystem as part of a framework's API?

I think it’s a part of their convention over configuration philosophy. Say what you will about it, there are obviously drawbacks. But I’ve noticed that it makes it easier to quickly understand new codebases in my organization. Everyone are using Next.js and all the apps have about the same file layout.

And it makes the routes easily greppable in VSCode/Ag/Telescope/CrtlP which I think is the thing motivating it.

I think it’s neat that having extremely fast project dir fuzzy finders has influenced framework design. Like how Django’s design is heavily influenced by how importlib works and would be completely different if Python modules worked differently.

Re: Fresh – Next-gen web framework

#92

Fresh = Deno version of Astro (static-first with SSR) and Isle (vue-focused) and bigger Next.js/Nuxt SSR (with no client js) modes. Remix also does well here with a focus on only SSR. It's basically what the original "isomorphic" javascript promise was to have the same code seamlessly running on server and client with a flexible split on what part ran where, now possible down to an individual tag/component. Also wort…

Does that mean JS running server-side? That's a full-stop dealbreaker for me.

Re: Fresh – Next-gen web framework

#94
post #93

Have other frameworks had the concept of ["interactive islands"]? I'd love to know more, but the docs aren't fleshed out yet. Does anyone know of other (documented) frameworks that use this concept? ["interactive islands"]: https://fresh.deno.dev/docs/concepts/islands

See astro: https://docs.astro.build/en/core-concepts/partial-hydration/...

Re: Fresh – Next-gen web framework

#95

Earlier quoted context omitted.

Have you seen Remix yet? It’s pretty compelling in terms of competition for Next.JS. It makes different trade offs and isn’t strictly better by every metric, but overall I’m very happy with it for the two use cases I’ve tried it with. It’s a very low overhead framework once the simple conventions click. I’d still like to check this out, then redwood and a couple others too. I’m not huge on these frameworks in general…

I've heard really good things about Remix, especially the nested routes. But I think Next is trying to copy that in Layouts? https://nextjs.org/blog/layouts-rfc I use Next not just for the routing and composition and hydration, but for all the other quality-of-life improvements (image resizing, buildchain configs, hot reload), especially when it's paired with Vercel (per-push sandbox builds, stale-while-revalidate, s…

Image resizing can’t be done statically. That’s a big issue if you want to serve things from cdn property.

Re: Fresh – Next-gen web framework

#96

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

It’s actually not gibberish.

* Island refers to this https://jasonformat.com/islands-architecture/

* Island based hydration is a form of partial hydration where the boundary is the component islands.

Re: Fresh – Next-gen web framework

#97

Fresh = Deno version of Astro (static-first with SSR) and Isle (vue-focused) and bigger Next.js/Nuxt SSR (with no client js) modes. Remix also does well here with a focus on only SSR. It's basically what the original "isomorphic" javascript promise was to have the same code seamlessly running on server and client with a flexible split on what part ran where, now possible down to an individual tag/component. Also wort…

Does that mean JS running server-side? That's a full-stop dealbreaker for me.

Deno is a JS runtime like Node, so if that's not your thing then yeah, this isn't for you.

Re: Fresh – Next-gen web framework

#98

Fresh = Deno version of Astro (static-first with SSR) and Isle (vue-focused) and bigger Next.js/Nuxt SSR (with no client js) modes. Remix also does well here with a focus on only SSR. It's basically what the original "isomorphic" javascript promise was to have the same code seamlessly running on server and client with a flexible split on what part ran where, now possible down to an individual tag/component. Also wort…

> Deno version of Astro (static-first with SSR) and Isle (vue-focused) and bigger Next.js/Nuxt SSR (with no client js) modes.

I think you have just summoned Cthulhu.

Re: Fresh – Next-gen web framework

#100

Fresh = Deno version of Astro (static-first with SSR) and Isle (vue-focused) and bigger Next.js/Nuxt SSR (with no client js) modes. Remix also does well here with a focus on only SSR. It's basically what the original "isomorphic" javascript promise was to have the same code seamlessly running on server and client with a flexible split on what part ran where, now possible down to an individual tag/component. Also wort…

> code seamlessly running on server and client with a flexible split on where that would be

It's a sound idea. Ideally this would fall back nicely when JS is disabled to good old get/post requests. It'd enforce a stricter mental model of what's a "page" and the boundaries between them. Currently, with JS component libs, this concept is somewhat blurry.

Post reply on HN