Hacker News Reader

Comment by bobthepanda | Hacker News Reader

Redux, and later useContext, were invented specifically to eliminate prop drilling.

Right. And I think the point is that Redux is a godsend for some small percentage of products but for the vast majority the cure is worse than the disease. Simple and slightly verbose is just "better" as a general solution than the powerful but complex solutions you get with Redux.

Prop drilling wouldn’t be an issue in a functional language as partial application could solve this problem.

I think a lot of the issues with React in general has to do with attempting to contort JS into a functional language.

useContext can lead to some gnarly code.

The major issue, IMO, is that the DOM is just markup with an API grafted on, and so any framework attempting to add the slightest bit of composability or state management has to twist and turn itself to be compatible in all browsers.

And that's how we got here, because everyone wants to make their applications available on as many platforms as possible, without having to maintain five or six separate teams that have to coordinate a roadmap, and the browser is the only somewhat consistent way to do this.

> contort JS into a functional language

I made something last year in a functional style as I was fresh off the back of a few React jobs and projects. I got a proof of concept working but the code was awful to work with.

I took a couple of days to start over and rewrite it with OOP principles and it was in a much better state afterwards.

This is untrue. You can observe this in scalas implicits, which generate an insane mess in any medium to large codebase.

Reply on news.ycombinator.com