3 ms·
I won't make an argument for Angular or Flux/Redux because those are very opiniated frameworks that might be overkill or simply not at all how you want to go ab
by codemusings 11y ago
I won't make an argument for Angular or Flux/Redux because those are very opiniated frameworks that might be overkill or simply not at all how you want to go about your app's architecture.
But React is about the view. You can't possibly be convinced that manually traversing the dom is just as easy and expressive as using JSX. Even in the simplest of interactive (as in you need Javascript) components or pages.
React's concept and syntax is super easy to understand and perfect for modularizing the components of your app. The real problem IMHO is the tool chain. That's what drives developers unfamiliar with the ecosystem away. And of course the fact that it seems to change all the time. The first time I looked at React they rolled their own transpiler. Now Babel is the recommended way to go.
According to the tutorial page you should either use browserify or webpack. You don't have to - but without them stuff gets messy pretty quick. Of course if you pick one of these up you also have to learn how to use them and you will want plugin A, B and C to get to your simple Hello, World React App in the first place.
So yeah. That's why it's so easy to step away from that thinking why don't I just simply roll my own framework.
- marknutter 11y ago> 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. You don't have to use....
- true_religion 11y agoAre 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.
- marknutter 11y agoRelay and Falcor both remove the need for Flux, I believe, but those solutions involve the backend I believe.
- true_religion 11y agoYes. 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.
- jrgoj 11y agoOne thing that helps me overcome template/boilerplate paralysis is when there are a few sentences for each of the submodules that explain what they do, how they fit into the larger picture, and why they were chosen over similar alternatives.