An Update on Fresh(deno.com) Fresh is a simple web framework based on the latest web standards that we built and use quite heavily here at Deno. We’ve teased the next version for quite some time now, but haven’t yet cut a release. Rest assured we haven’t forgotten about it. In fact, a pre-release version of Fresh 2 is being used in production here at Deno — on our main website as well as on Deno Deploy.
How We Fell Out of Love with Next.js and Back in Love with Ruby on Rails(hardcover.app) This is part 1 of a series documenting Hardcover’s Alexandria release. We recently migrated our codebase from Next.js to Ruby on Rails, and it’s been amazing so far! It was a learning experience, and I’m excited to share some of our takeaways. I’ll link each article here as it’s written.
5 points by handfuloflight 67 days ago | 0 comments
Library patterns: Why frameworks are evil(tomasp.net) This article is a follow up to my previous blog post about functional library design, but you do not need to read the previous one, because I'll focus on a different topic.
We Moved Off Next.js(documenso.com) When we started building Documenso, choosing Next.js was a no-brainer. We wanted SSR (server-side rendering), easy routing, and the vibrant community that came with it. It helped us ship fast, iterate quickly, and provided all the essentials in one neat package. For a while, it was exactly what we needed.
Show HN: Wasp – the first full-stack framework powered by an LLM(wasp.sh) For those of you who are new here, we have been building a full-stack, batteries-included web framework for the last four years. You can think of Wasp as a modern, JS-based incarnation of Laravel, Django or Ruby on Rails. We based it on a custom compiler so it doesn’t depend on the specific stack or the architecture in the long run (currently it supports React, Node.js and Prisma).