146 karma · joined October 11, 2016
Check out this one too https://www.kalzumeus.com/2011/10/28/dont-call-yourself-a-pr...
Of course, I do that a lot with generic, reusable components. Once I know it's too complex I extract it to model that gets passed through props. Win/win
I'm a big fan of MobX and it pains me to no end that it didn't took off better. It's a godsend from like 5 years ago and it makes so many of these React pain points disappear.
Instead of adding state to your components here and there, it works outside of the view layer. You define the model, derived computed views, actions and then just use it inside your components. You never ever worry about performance because MobX knows what is used where and it will optimize your renders automatically.
Moreover, dealing with state outside of the view layer makes it much more easier to refactor, reason about and test your app. Sure, you can do the same with Redux but it's 10x more code.
I recommend this article on this topic by the author - https://michel.codes/blogs/ui-as-an-afterthought
But why does a site aimed on Apple products has it is mindboggling
Edit: actually I did use .bind with React before arrow functions came
I'd be fine to pay such amount if the app was polished and had great UX. Not arguing with what you stated.
Seems like this is a common thing people need and I too tried to make an app for this. I gave up on it because the complexity grew fast, but my plan was to release it for free and have some sort of premium. I wanted to have a good product first before asking for money.