vcarl•2y ago

If you use React, you should be using a React framework

Tweets from acdlite. Whatcha think? https://twitter.com/acdlite/status/1617611126514266112 https://twitter.com/acdlite/status/1617611127982284800 https://twitter.com/acdlite/status/1617611129282527232 https://twitter.com/acdlite/status/1617611131039940608 https://twitter.com/acdlite/status/1617611133216788480 https://twitter.com/acdlite/status/1617667095759835136 https://twitter.com/acdlite/status/1617667097424986114

Andrew Clark (@acdlite)

If you use React, you should be using a React framework. If your existing app doesn't use a framework, you should incrementally migrate to one. If you're creating a new React project, you should use a framework from the beginning.

Likes

1404

Retweets

144

Twitter

Andrew Clark (@acdlite)

Your React framework of choice should have built-in solutions for data fetching, routing, and server rendering. Frameworks don't treat these as independent concerns — they provide deeply integrated solutions that are easy to use and result in excellent performance out of the box.

Likes

136

Twitter

Andrew Clark (@acdlite)

Which framework you choose is an important decision, but it's much less important than choosing to go with a framework in the first place. Personally, I'd go with Next.js, Remix, or Expo.

Likes

170

Twitter

Andrew Clark (@acdlite)

If you choose to forgo a framework, what you're really choosing is to build your own bespoke framework, one that's likely much worse than what you'd get off the shelf. Even if you think your bespoke framework is better than the alternatives today, will that be true in a year?

Likes

135

Twitter

Andrew Clark (@acdlite)

It takes lots of time and energy to keep up with the state of the art. Are you ready to become a framework maintainer? Or are there better things you should be doing with your time?

Twitter

6 Replies

vcarl•2y ago

I generally agree tbh. Data fetching alone, I think, is reason enough to have something help do the heavy lifting. If you have SSR needs (and virtually every app is improved by adding the ability to pre-render something before clientside JS loads), then building your own from scratch is 100% building a custom framework

vcarl•2y ago

I was watching this, and he talks about the need to own the server to provide some of the dev experience they intend to, which seems to line up with this as well https://www.youtube.com/watch?v=C1m5hQDjk20

Real World React

YouTube

Reflections on a career managing React with Tom Occhino

Tom Occhino is a former Facebook Engineering Director who helped create React and React Native. After joining the company as a software engineer in 2009 he helped develop user-facing products, core front-end infrastructure, and Facebook's open source program. As an engineering manager and director he was responsible for the JavaScript infrastruc...

lebouwski•2y ago

I have literally 0 benefit from SSR, it's a CRUD app behind a login screen nextjs provides nothing that'll improve that experience loading data 'per page request' is the wrong abstraction and the app folder is half baked at the moment SSR would be fine for the initial request I just want it to be CSR+offline first after that

Unknown User•2y ago

Message Not Public

vcarl•2y ago

yeah i gotta say i LOVE the exports pattern, and i can sense how complex the build process for making it work is. really nice experience for the most part

export const loader = …
export const action = …
export default …

export const loader = …
export const action = …
export default …

Unknown User•2y ago

Message Not Public