React Pain Points - solasistim.net

formatted unclear questions and as a result, users with the requisite experience to answer the relevant questions don't have the patience to monitor the channel. As a result, even asking extremely clear questions with definite answers don't get the same response as you would get on (for instance) `#c++` on freenode. … docuemntation?), in practice project *X* is far more likely to be structured similarly to project *Y* in Vue than React. Unacceptable levels of boilerplate when creating forms. I don't think I need to demonstrate, even React fans admit that it's not where the toolkit shines (and Vue competes badly here too when Vuex is in use; AngularJS is better). APIs like Formik are ludicrously complicated for what they do. I think that traditional server-side web frameworks are far better at handling applications that are basically forms, which is a surprising number of applications. … write-only mess? Also, what the hell is a Saga and why do I need it? Create-react-app sucks with its 'eject' concept. Why say: "Stick 100% with the preset, or completely dissociate from us and never get any updates"? Surely it's not beyond the wit of man to form an abstraction on top of the C-R-A … Every time you want to do a conditional or a branching statement you essentially have to factor the conditional into a new functional component, that or use an ugly ternary. Again, very principled, but not very ergonomic. The lack of first-class IDE support makes this one a particular pain, since it shows