3 ms·

RedwoodSDK – a composable framework for building server-side web apps

10 points by johndevor 1y ago

osener 1y ago
Music to my ears. I’ve been trying to get close to what this promises using Remix/React Router v7 or Hono. It’s the best approach for a solo maker/small team, but it always feels like a thousand papercuts. On the other side, there’s Vercel + Next.js — the straight-up guillotine. These folks really seem to get it. I’ll be keeping a close eye on this one.
vhsdev 1y ago
May I live a thousand years and never hunt again.
tenga 1y ago
I like this! https://rwsdk.com/personal-software https://rwsdk.com/personal-software "We believe software can be personal again. Not just technically, but philosophically. Owned. Forkable. Shareable. Local. Beautiful. Built for use, not for scale. Built with love, not venture funding. Built for yourself - and maybe a few others. If this resonates with you, come join us. We're not just building a framework. We're building a future where software is yours again."
redbar0n 1y ago
This was clarifying: https://redwoodjs.com/blog/redwoodsdk https://redwoodjs.com/blog/redwoodsdk See also earlier thread: https://news.ycombinator.com/item?id=43592998 https://news.ycombinator.com/item?id=43592998 RedwoodJS is going into maintenance mode and is named Redwood GraphQL. RedwoodSDK is the focus for the team going forward. "It begins as a Vite plugin that unlocks SSR, React Server Components, Server Functions, and realtime features". Which reminds me of the modular approach of Vike.dev (aka. vite-plugin-ssr). Seems like the unbundled and modular approach won over the opinionated fullstack all-in-one framework approach.
- redbar0n 1y ago
  Unbundled won over bundled approach, even for RedwoodJS itself (which is now renamed Redwood GraphQL): "Unbundled Integrations: Over the coming months, we'll progressively unbundle third-party integrations—such as the authentication providers, Storybook, and others. These integrations will then be independently maintained by their original teams or the community, giving you greater flexibility, faster updates, and control over which integrations you adopt and support." https://web.archive.org/web/20250407165256/https://redwoodjs.com/ https://web.archive.org/web/20250407165256/https://redwoodjs...

10 points by johndevor 1y ago

Music to my ears. I’ve been trying to get close to what this promises using Remix/React Router v7 or Hono. It’s the best approach for a solo maker/small team, but it always feels like a thousand papercuts. On the other side, there’s Vercel + Next.js — the straight-up guillotine. These folks really seem to get it. I’ll be keeping a close eye on this one.

vhsdev 1y ago

May I live a thousand years and never hunt again.

tenga 1y ago

I like this! https://rwsdk.com/personal-software https://rwsdk.com/personal-software "We believe software can be personal again. Not just technically, but philosophically. Owned. Forkable. Shareable. Local. Beautiful. Built for use, not for scale. Built with love, not venture funding. Built for yourself - and maybe a few others. If this resonates with you, come join us. We're not just building a framework. We're building a future where software is yours again."

redbar0n 1y ago

This was clarifying: https://redwoodjs.com/blog/redwoodsdk https://redwoodjs.com/blog/redwoodsdk See also earlier thread: https://news.ycombinator.com/item?id=43592998 https://news.ycombinator.com/item?id=43592998 RedwoodJS is going into maintenance mode and is named Redwood GraphQL. RedwoodSDK is the focus for the team going forward. "It begins as a Vite plugin that unlocks SSR, React Server Components, Server Functions, and realtime features". Which reminds me of the modular approach of Vike.dev (aka. vite-plugin-ssr). Seems like the unbundled and modular approach won over the opinionated fullstack all-in-one framework approach.

redbar0n 1y ago
Unbundled won over bundled approach, even for RedwoodJS itself (which is now renamed Redwood GraphQL): "Unbundled Integrations: Over the coming months, we'll progressively unbundle third-party integrations—such as the authentication providers, Storybook, and others. These integrations will then be independently maintained by their original teams or the community, giving you greater flexibility, faster updates, and control over which integrations you adopt and support." https://web.archive.org/web/20250407165256/https://redwoodjs.com/ https://web.archive.org/web/20250407165256/https://redwoodjs...