# A quick review of the Fresh web framework Unless you have been living under a rock, then you probably have heard of [Fresh](https://fresh.deno.dev/), the shiny new TypeScript web framework. Fresh boasts some impressive features, such as: - No build step - No config needed - TypeScript support out of the box - No JavaScript is shipped to the client by default But how good is Fresh in terms of developer experience? To answer that question, I have built a simple file-system based pastebin service, called [Petunia](https://github.com/HoangTuan110/petunia), using Fresh and Deno. Short answer? Fresh is pretty good if you already know React and Tailwind, though it has some quirks that you have to get used to, like handling input. The longer answer? Fresh relies on [Preact](https://preactjs.com/)--a lightweight version of React--to display components, so if you are a React developer, then Fresh should feel like home to you. When initializing a new project, Fresh will also ask if you want to use [Twind](https://twind.dev/), which is a Tailwind-to-JS library. If you choose this option, then you will have the power of Tailwind without creating a config file or using PostCSS, which I thought is pretty cool. Here are a few things to notice though: - Fresh uses [NextJS's file-system based routing](https://nextjs.org/docs/routing/introduction), so for example `routes/link/[id].ts` becomes `/link/:id` in the web app. - The way Fresh handles form submission is very different from React. Instead of using states like React, Fresh takes advantage of the HTML `