5 ms·

React is simple. First I'd start with creating the database in Postgres. Create tables to hold data and any views needed to represent joined tables for conveni

React is simple. First I'd start with creating the database in Postgres. Create tables to hold data and any views needed to represent joined tables for convenience. Once that's settled, the express server comes next to create a CRUD API to work with the data and handle user authentication and authorization. This is dead simple and once it works there's little you need to touch. The database handles any data dependent business logic. By this point you can make API calls and use the application through any REST client. So now I just need to create a React client to consume the API and give a great user experience. Don't need Redux. Grab React-Router and a couple packages for UI components and you'll be up and running with the MVP in no time. Checkmate.

goatlover 8y ago
> Create tables to hold data and any views needed to represent joined tables for convenience. Once that's settled, the express server comes next to create a CRUD API to work with the data and handle user authentication and authorization. Not sure how you're beating Rails or Django at this, unless you're a 10X developer going against a normal one. For that matter, I'm willing to bet an experienced Drupal developer using drush would be faster setting things up.
- matte_black 8y ago
  I don't think being able to write some simple SQL makes you a 10x developer. I think it's normal. The way I prefer to see it is relying on ORMs makes you a weak developer.
  - goatlover 8y ago
    This is about how fast someone experienced in Rails/Django/Drupal/Laravel could get a basic CRUD app up and running vs. a JS framework.
    - spiritcat 8y ago
      If you're familiar with setting up a basic express app, and kind of know how you like to do things, can prob set up another one pretty quickly. None of the ORM's prob as mature on node (last i checked) but still not a huge amount of friction if you already know one. Node will prob take longer if you're taking time to try out [new hotness lib of the day], though.

goatlover 8y ago

> Create tables to hold data and any views needed to represent joined tables for convenience. Once that's settled, the express server comes next to create a CRUD API to work with the data and handle user authentication and authorization. Not sure how you're beating Rails or Django at this, unless you're a 10X developer going against a normal one. For that matter, I'm willing to bet an experienced Drupal developer using drush would be faster setting things up.

matte_black 8y ago
I don't think being able to write some simple SQL makes you a 10x developer. I think it's normal. The way I prefer to see it is relying on ORMs makes you a weak developer.
- goatlover 8y ago
  This is about how fast someone experienced in Rails/Django/Drupal/Laravel could get a basic CRUD app up and running vs. a JS framework.
  - spiritcat 8y ago
    If you're familiar with setting up a basic express app, and kind of know how you like to do things, can prob set up another one pretty quickly. None of the ORM's prob as mature on node (last i checked) but still not a huge amount of friction if you already know one. Node will prob take longer if you're taking time to try out [new hotness lib of the day], though.