3 ms·
RedwoodJS. I feel like I am the only one to ever mention it on HN. It feels like I know a secret that no one else knows. Here's how the landing page describes
by Graffur 5y ago
RedwoodJS. I feel like I am the only one to ever mention it on HN. It feels like I know a secret that no one else knows.
Here's how the landing page describes it " Built on React, GraphQL, and Prisma, with full TypeScript support, and Webpack/Babel ready to go with zero config. Redwood gives you the workflow you love, but with simple conventions and helpers to make your experience even better. "
- hkarthik 5y agoI played with RedwoodJS over the holidays and there is a lot to like. However it does paper over a lot of complex things with fairly leaky abstractions currently. Expect to have to understand how GraphQL, Prisma, and React work whenever you encounter something that doesn't quite work. This is not uncommon with most frameworks in the early days. I used Ruby on Rails since just before 2.0 and it was similar back then. But the team behind RedwoodJS is great, and there's a nice community on Github, Discourse, and Discord. So I'm expecting great things. Plus it's nice to have an omakase approach to learning all of the new frontend tech and getting something working quickly.
- Graffur 5y agoI haven't hit that yet. One of the principals I am following in my side project is to keep everything as simple as possible (he says while using a JS stack!). I know React but have been getting to grips with using GraphQL and Prisma. TIL what omakase means. Thanks!