Hacker News Reader

What’s the reason to avoid class components though? The official tutorial still uses it, though that could just be because it’s outdated?

View on HN

The React team is currently working on a complete rewrite of the docs, which will include a focus on hooks first:

https://github.com/reactjs/reactjs.org/issues/3308

In the meantime, someone else ported the existing docs to teach function components and hooks in the examples:

https://reactwithhooks.netlify.app/

The zeitgeist is that hooks are easier to reason about than life cycle methods, functional components are more lightweight and result in less bundled code.

It's more of a hype train than a "zeitgeist". Major community contributors like Jared Palmer have stepped forward in the past year to critique the complexity of React hooks.

https://jaredpalmer.com/blog/react-is-becoming-a-black-box

https://dillonshook.com/a-critique-of-react-hooks-addendum/

Personally, I think blindly adopting the latest frontend trends is the opposite of being "radically pragmatic".

What's more pragmatic than not being precious about what technology decision is most perfect and instead going with what's popular and has a lot of community support?

Ok! Your opinion is noted

Reply on news.ycombinator.com