> You don't have to - but without them stuff gets messy pretty quick.
Which is the same as saying "you have to".
Can't we just accept that developing with React is no longer as simple as just stitching some views together? It's as if the collective React community is very insecure about the fact that writing web applications is gonna be hard and complicated no matter how shiny your tools are.
Sure, you don't have to use JSX, but without it stuff gets messy pretty quick.
And you don't have to use flux/redux, but without it stuff gets messy pretty quick.
Also, you don't have to use ReactRouter, but without it stuff gets messy pretty quick.
Are there any other options out there part from Flux/Redux patterns?
I've been looking into using React (well for the past 4 days of solid research), but I'm finding that pure reducers are a mental-mismatch for me.
I'd like something that helps me manage state, and perhaps constraints its flow (like Reach does with unidirecitonal renddering), but not something that tries to abstract state away completely.
Yes. That's true. I've found out about GraphQL lately, which seems to be with a real possibility for me to use since I have a python backend and Graphene will help with creating an api for GraphQL to consume.
Which is the same as saying "you have to".
Can't we just accept that developing with React is no longer as simple as just stitching some views together? It's as if the collective React community is very insecure about the fact that writing web applications is gonna be hard and complicated no matter how shiny your tools are.
Sure, you don't have to use JSX, but without it stuff gets messy pretty quick.
And you don't have to use flux/redux, but without it stuff gets messy pretty quick.
Also, you don't have to use ReactRouter, but without it stuff gets messy pretty quick.
You don't have to use....