As a subset of the JS community, react has seen a lot of so-called ""good practices"" these last years, made out of libraries and design patterns. As if it wasn't hard enough to stay sane in a crazy JS world, we're now doing the same in react.
Together, let's explore how such abundance of new techniques can actually be embraced, without making you lose your mind !
! Yearly ES spec
! New libraries, features
! New good practices
! Imposter syndrome
! TS is now the industry standard
! Node is now required for front/back-end
! Tooling complexity (webpack, babel) = Entry barrier 😪
Full-stack « Frameworks »
Vulcan is unique in that it spans the full stack, from the database to the browser.
While there exists many excellent back-end frameworks or backend-as-a-service
providers, these all still require you to handle your front-end code yourself,
including building a set of components to read, write, and display data.
But because Vulcan is full-stack, it’s able to speed up these repetitive tasks by
providing a whole range of helper components that are ﬁne-tuned to the Vulcan back-
end, and as a result just work out of the box.
Well… not only !
! Query-Component colocation
! Reduces redux usage
! Complete ecosystem with optimistic UI updates, caching etc (apollo-
! New pattern to learn
! New concepts to learn if you use relay
! Defines your app architecture
Seriously, don’t go full hipster
! Keep it clean
○ One lib/technology per pattern
○ Isolated parts of your app
○ Refactor if/after you ditch that pattern/library
○ No conflicting patterns 🏆
! Side projects are cool !
! Don’t forget why you chose a library vs. a framework 🎉
! Skeptical mindset
! React Fatigue is a strength
! Embrace the ecosystem ⚛
! Stay curious
○ Read about new libs / patterns
○ Analytic mind on trends
○ Don’t always go with the community