I was very interested in how Deno would evolve a while ago, but have completely lost track.

Can anyone explain the gist of what Fresh is and its relation to Deno? Just asking because the domain is deno.com

A lot of the ideas around TypeScript and module resolution, ESM import maps seemed reasonable when Deno was announced.

Then the "islands" concept sounded interesting to me - every build system ends up doing something like this, right?

But the examples look like htmx or Laravel Templates to me. I can't follow the syntax and it seems hard to see the client/server boundaries.

Along that line, what has Tailwind have to do with all this?

Deno is a JS runtime aiming to replace Node, with some bundling capabilities. Fresh is a web framework built on Deno. Is that correct?

Yes, Deno is a Typescript runtime with some nifty additions. Fresh is a web framework similar to Next.js that builds on the philosophy of Deno. It supports the popular Tailwind (via Twind) for styling.

Thanks! I hope Deno finds more adoption in the future, I am always interested in full stack TS frameworks, next.js has a very broad market share (deservedly so).

Recently I tried vite-plugin-ssr for a simple brochure page hosted as static files, it went pretty well. But of course this tool introduced its own abstractions.

The tendency to build things into the platform (if I understand the Deno philosophy correctly) could really help with fragmentation.

OTOH, an obligatory XKCD about standards comes to mind here...

Very excited to see how Fresh is coming along. It is a joy to use and its implementation of the islands just feels effortless.

Exciting to see how consistently Fresh is improving.

We're trying out Deno and Fresh on a recent project and it's been excellent so far.

Only downside is the limited plugin ecosystem (would love to see some Zod schema validation and OpenAPI plugins for API routes, for example)