> I'd go as far as to say class-based components are strictly inferior because they force you split your behavior logic across lifecycle methods and are not ea

> I'd go as far as to say class-based components are strictly inferior because they force you split your behavior logic across lifecycle methods and are not easily composable. That's not strictly true. You can implement "hooks" on top of a class based components. It's essentially the strategy pattern.