Write a Higher Order Component from Scratch

Why should I be writing 'high order components'? I do not understand what they do for me, it seems like a lot of abstraction with no clear benefit.

Austin you nailed it, this was my point. There's actually a lot of benefits from higher order components, but it's not being explained. That's where some type of small intro to these videos would not only be extremely beneficial but in some cases crucial to understand the material. I understand that egghead tries this 'bite size' approach of training which is fine, it's great for breaking up the material but that's not a replacement method of teaching if you don't have some context with a beginning, middle and end.

I think the remaining lessons in the course help answer your question through various examples. I'm optimistic that by the end of the course you'll have a clear understanding of why you might use HOCs. This particular lesson was added to the beginning to demystifying what HOCs do "under the hood". I could move it later in the course after learners have gotten some initial exposure to some several real world examples.

Alright Tim, I trust you and I will give it a go! A short introduction is always useful in any case, for my taste. But opinions opinions.

Thanks for the quick reply :thumbsup:

It's good feedback. Thank you.

Instead of neverRender you mean neverUpdate, right?

Cool... just a bit dry 😬

which videos on egghead r are prerequisites? thx

why do you write BaseComponents in curly brackets without parentheses?

const neverRender = {BaseComponent} => class extends Component { shouldComponentUpdate() { return false; } render() { return <BaseComponent {...this.props} />; } };

...

const User2 = neverRender(User)