News for hackers. Stuff that matters.
Re:RedwoodJS 1.0 by sandwichinvest on Monday April 04, 2022 @12:16PM (#30908371)
If your other option is "raw" React, Next.js: You'll do less yak-shaving and have to manage less engineering complexity versus using Next.js and rolling your own db/auth/testing/access control.

If your other option is Blitz: you get a larger core team, GraphQL if you like that, and fancier generators.

If your other option is Django/Rails/etc: it is like Rails, but integrates better with the frontend.

Re:RedwoodJS 1.0 by leodriesch on Monday April 04, 2022 @12:41PM (#30908724)
Django/Rails comparison is a bit short I would argue, Redwood lacks a lot of their backend capabilities (Active Storage, mailing solution, jobs, Action Cable).
Re:RedwoodJS 1.0 by adfm on Monday April 04, 2022 @03:57PM (#30911298)
Add simplicity to your list. Tools like htmx and hotwire appeal to me because they cut down on the towering stack of fast-moving parts.
Re:RedwoodJS 1.0 by midrus on Wednesday April 06, 2022 @01:51AM (#30928881)
Have you tried Unpoly? It's like htmx but more "high level". I've used it for several projects and it is one of the more underrated tools out there. On my latest project.im using it in combination with Alpine.js on a Laravel application and I'm loving it.
Re:RedwoodJS 1.0 by midrus on Wednesday April 06, 2022 @01:49AM (#30928868)
>If your other option is Django/Rails/etc: it is like Rails, but integrates better with the frontend.

And worse with the backend.

Let's not pretend running code in the server are issuing queries to a database is all you do in the backend.

Re:RedwoodJS 1.0 by flybayer on Monday April 04, 2022 @02:09PM (#30910029)
Blitz doesn’t use GraphQL, one of the unique things about it.