mddilley
commented
7 months ago Notes:
- Read the quickstart https://remix.run/docs/en/main/start/quickstart
- Started the tutorial https://remix.run/docs/en/main/start/tutorial
Arc Easel:
Content:
Why use a React framework?
- Developer experience
- Make less choices
- Make the hard parts easier and routine
- Gives out of the box way to implement server side rendering, client side rendering, or a mix of box
- Make an app feel great to users without having to figure out all of the details on your own
- All of this adds up to a faster way to create value for users
What have we used to make React apps?
- Create React App which used to be “the way” to bootstrap a React app but is now deprecated
- Next.js which is an amazing React framework that is widely adopted and has a great community. They’ve made exciting developments that are shaking up the web dev world.
Links:
- https://www.epicweb.dev/why-i-wont-use-nextjs
- https://leerob.io/blog/using-nextjs
- https://remix.run/
Pros 🙌:
- Recently incorporated Vite so local development is super fast and opens the door to its ecosystem
- TypeScript
- Data mutations like updates or inserts use HTML forms that send data to what they call “actions” (place to define what to do next)
- “Loaders” get data and “actions” accept data and then revalidate after they are done
- They claim to stick to web standards and their docs prove it - lots of links to Mozilla MDN docs
- TIL about placekitten.com
Not sure about 🤔:
- Flexible config which is nice but also that means more decisions
- File-based routing vs. folder-based
- Routing file syntax seems confusing but I’m also a newbie
What is next?:
- See how this framework works on a larger project
- Get a better feel for how loaders bring data into the app in parallel
- Test it with a real backend
- Explore their take on optimistic UI
Motivated by Kent C Dodds blog post: https://www.epicweb.dev/why-i-wont-use-nextjs
Resources