Brandon Bayer

Blitz.js — a Rails-like framework for full-stack React apps without an API  ↦

Brandon Bayer:

The central thesis is that most apps don’t need a REST or GraphQL API. Blitz brings back the simplicity of server rendered frameworks like Ruby on Rails while preserving everything we love about React.

Additionally, Blitz is bringing other Rails goodness that’s missing in the React ecosystem like file structure and routing conventions, a really nice console REPL, intelligent code-scaffolding, and a fine-tuned out-of-the-box setup with Prettier, Typescript, ESlint, Jest, Cypress, etc.

The framework ‘wars’ continue right alongside the monolith-vs-microservices debate. For more on the principles behind Blitz, check out the manifesto.


Sign in or Join to comment or subscribe

Jerod Santo

Jerod Santo

Omaha, Nebraska

Jerod co-hosts The Changelog, crashes JS Party, and takes out the trash (his old code) once in awhile.

2020-04-06T16:57:05Z ago

I find it interesting that Blitz and Redwood are springing onto the scene at relatively the same time.

⭐ Both are full-stack frameworks for React apps
⭐ Both are heavily inspired by Ruby on Rails

BUT Redwood is all about APIs and pre-rendering while Blitz is all about server-side rendering…

2020-04-07T03:07:00Z ago

Yeah, it is interesting!

So Blitz isn’t all about SSR. Back at the initial announcement, SSR was the key thing, but this is no longer the case. Blitz pages can be fully static shells with data loaded on the client or they can be SSR. And you can choose static vs SSR on a page by page basis.

The core difference between Redwood and Blitz is that Blitz uses RPC and Redwood uses GraphQL. The second biggest difference is that Blitz is built on Next.js (so you get everything Next provides, including custom API routes), but Redwood is built on their own custom webpack setup.

Player art
  0:00 / 0:00