3 ms·

Completely agree. My default stack is now react + an api in the backend. The way you can reuse components is a great time saver (even for simple apps). I also

Completely agree. My default stack is now react + an api in the backend. The way you can reuse components is a great time saver (even for simple apps). I also like redux-thunk to separate all my API calls from the components. Makes everything very lean and readable. I feel way more productive today than in the old jQuery, knockout messes

r_singh 7y ago
Same here! What's your choice of stack for the api? PS - I need to build an api for an app with a React front-end. My choice of language is Python (because I'm super familiar and because of the great ORMs Python has).
- orhanhh 7y ago
  Django-rest-framework is super productive once you learn it. It has a bit of a learning curve, but it’s worth it if you are writing a lot of APIs, especially if you’re doing a lot of CRUD. It’s my go to tool when I need to get stuff done. Combined with react and typescript, developing full stack is really smooth.
jeremija 7y ago
I've started to use TypeScript and React on the front end, with a JSON RPC middleware on an express server with helpers that automatically implement service interfaces for API calls, action creators and reducer handlers. And all of them are type-safe. I've spent a lot of time building CRUD APIs and GraphQL interfaces, and this is the simplest solution that has saved me so much development time. JSON RPC gets so much hate, but it's made my life so much simpler.
- NohatCoder 7y ago
  Sounds neat, what project are you working on?
  - jeremija 7y ago
    I'm currently working on various projects at work that I cannot discuss here, but in parallel I've been working on an express / TypeORM / React (SPA & SSR) framework that I hope to release one day as an open source project. The main focus is to: - easily share React components that use Redux state and actions between projects - rapidly develop new server-side services and immediately use them in React components (by removing code duplication when it comes to creating action creators and action types) - have type safety - provide basic server-side and client-side components for basic user actions such as login, user profile, etc - make it easy to write tests And at some point in the future, I hope to make it generic enough so the libraries mentioned above can be swapped for other libraries, but that might be too much work :)
    - NohatCoder 7y ago
      Sounds like a lot of work, how do you know that it is a net time saver?
      - jeremija 7y ago
        Haha, I guess it is not at the moment, but it keeps me amused. In the first post I was just referring to using JSONRPC over standard REST endpoints as the time saver.

r_singh 7y ago

Same here! What's your choice of stack for the api? PS - I need to build an api for an app with a React front-end. My choice of language is Python (because I'm super familiar and because of the great ORMs Python has).

orhanhh 7y ago
Django-rest-framework is super productive once you learn it. It has a bit of a learning curve, but it’s worth it if you are writing a lot of APIs, especially if you’re doing a lot of CRUD. It’s my go to tool when I need to get stuff done. Combined with react and typescript, developing full stack is really smooth.

jeremija 7y ago

I've started to use TypeScript and React on the front end, with a JSON RPC middleware on an express server with helpers that automatically implement service interfaces for API calls, action creators and reducer handlers. And all of them are type-safe. I've spent a lot of time building CRUD APIs and GraphQL interfaces, and this is the simplest solution that has saved me so much development time. JSON RPC gets so much hate, but it's made my life so much simpler.

NohatCoder 7y ago
Sounds neat, what project are you working on?
- jeremija 7y ago
  I'm currently working on various projects at work that I cannot discuss here, but in parallel I've been working on an express / TypeORM / React (SPA & SSR) framework that I hope to release one day as an open source project. The main focus is to: - easily share React components that use Redux state and actions between projects - rapidly develop new server-side services and immediately use them in React components (by removing code duplication when it comes to creating action creators and action types) - have type safety - provide basic server-side and client-side components for basic user actions such as login, user profile, etc - make it easy to write tests And at some point in the future, I hope to make it generic enough so the libraries mentioned above can be swapped for other libraries, but that might be too much work :)
  - NohatCoder 7y ago
    Sounds like a lot of work, how do you know that it is a net time saver?
    - jeremija 7y ago
      Haha, I guess it is not at the moment, but it keeps me amused. In the first post I was just referring to using JSONRPC over standard REST endpoints as the time saver.