4 ms·

I'm surprised nobody has mentioned https://redwoodjs.com https://redwoodjs.com Here's why I'd pick it: 1. One language for the whole stack. It's an MVP so the

by turadg 4y ago

I'm surprised nobody has mentioned https://redwoodjs.com https://redwoodjs.com Here's why I'd pick it: 1. One language for the whole stack. It's an MVP so the front and back are both changing fast, with changes made by the same person, and you don't want to context switch all the time. 1a. Javascript as that language because it's the most flexible. And with TypeScript you can gradually opt into type constraints where they help you. 2. An opinionated full stack like Ruby on Rails that integrates all the pieces I need to ship. When you assemble yourself, even small version bumps or outdated tutorials can send you down a rabbit hole, stealing time from testing PMF. You want someone to validate a combination in which all the pieces work together smoothly. 2a. Redwood.js closest to be being the Ruby on Rails of JavaScript. I've toyed with it before and got up and running quickly. Its opinions took a lot of unimportant decisions out of my hands and let me focus on what I was trying to produce. I didn't get so far as to confirm this but it also seems to make it easy to gradually drop the scaffolding if the opinions and simplifications ever get in your way.

dbbk 4y ago
I've never been much a fan of Node for backends though. There's no framework that's as feature packed as, for example, Laravel on PHP. And you have to worry about leaking state/memory across requests.
- 0xblinq 4y ago
  THIS.
0xblinq 4y ago
None of these frameworks (next.js, remix, redwood, etc, etc, etc) is a even half close to what you need for any non-trivial MVP backend. Such as: - Validations - Translations/localization - Error and request logging and auditing - Security (CQRS, CORS, CSRF) - Permissions and a way to integrate it with your authentication (does supabase handle this? don't know) - Email sending - Background jobs - Caching - File uploading - Rate limiting Several of these very important things are missing for all of these frameworks. While most of them come by default or with community maintained "de facto" solutions. I'm yet to see a feature wise equivalent framework in the JS world to laravel/django/rails. They're batteries included or full stack just on the surface, as soon as you start using them you start missing a ton of stuff.

by turadg 4y ago

dbbk 4y ago

I've never been much a fan of Node for backends though. There's no framework that's as feature packed as, for example, Laravel on PHP. And you have to worry about leaking state/memory across requests.

0xblinq 4y ago
THIS.

0xblinq 4y ago

None of these frameworks (next.js, remix, redwood, etc, etc, etc) is a even half close to what you need for any non-trivial MVP backend. Such as: - Validations - Translations/localization - Error and request logging and auditing - Security (CQRS, CORS, CSRF) - Permissions and a way to integrate it with your authentication (does supabase handle this? don't know) - Email sending - Background jobs - Caching - File uploading - Rate limiting Several of these very important things are missing for all of these frameworks. While most of them come by default or with community maintained "de facto" solutions. I'm yet to see a feature wise equivalent framework in the JS world to laravel/django/rails. They're batteries included or full stack just on the surface, as soon as you start using them you start missing a ton of stuff.