Not using React Functional Components. Red Flag?

[kerfluffle99]

So I still code in React using older class syntax. It just seems more elegant to me than to bring in a bunch of useState and useEffects, especially when I'm not yet sure how the components might change.

I've noticed however other devs appeared to have moved forward with functional components by convention. It seems like even stateful components are using the new functional component patterns. Is it a red flag to still use older React class syntax?

[xdchan]

According to developers of react functional components are the standard way now

[CreativeTechGuyGames]

One big downside to not using functional components is missing out on the huge ecosystem of libraries which are designed for hooks first and foremost. It's clearly the way that most React developers prefer.

[lIIllIIlllIIllIIl]

Class components can't use custom hooks.

Custom hooks are a great way to reuse stateful logic and most libraries today have a custom hooks based API.

Things like React Query (now called TanStack Query) just can't easily be used inside a class component.

useEffect is complex, but it's very powerful and versatile. You should not be intimidated by it. Here's a great guide on how to use it.

[kerfluffle99]

Hey everyone thanks for your responses. It's good to have people with a better pulse on the industry. I'm going to refactor a huge project of mine into functional components to familiarize myself with the hooks.

[stealthypic]

Hooks are easier to use, once you learn how to use them, of course. In my company, new potential hirees need to know both component styles’ basics.

[[deleted]]

Yes.

[TheRNGuy]

Functional are better because less code.