what's the point of presenting this as a flowchart?
React Makes You Sad?
61–70 of 211 posts
Re: React Makes You Sad?
#62React made me sad, so I switched to Mithril[1]. Not only is it significantly smaller in size, but it's way faster and includes a router and AJAX methods out of the box. I wish more people would give it a shot. That said, I do still love React Native, and use React on a daily basis to take advantage of the "write once, run anywhere" paradigm. [1] https://lhorie.github.io/mithril/
The React Native approach is actually "learn once, write anywhere." https://code.facebook.com/posts/1014532261909640/react-nativ...
Those are just slogans, like Java's was.
In practice you'll learn React Native once (1), learn some of each platform's intricacies (N), and sometimes need to debug (at most for each platform, so 0...N.
Re: React Makes You Sad?
#63Earlier quoted context omitted.
Agreed. I was kind of shocked to open up the comments and see people taking this at face value. I know this isn't reddit, but "upvoted because React" seems to be just as much in play over here.
I lol'd the minute I saw the flow chart. It's absurd. Helpful and well-intentioned, but absurd.
Thank you for the criticism! Would you like to help me understand its flaws better so I can improve in the future?
Re: React Makes You Sad?
#64React made me sad, so I switched to Mithril[1]. Not only is it significantly smaller in size, but it's way faster and includes a router and AJAX methods out of the box. I wish more people would give it a shot. That said, I do still love React Native, and use React on a daily basis to take advantage of the "write once, run anywhere" paradigm. [1] https://lhorie.github.io/mithril/
Project seems abandoned, no?
I'm working on a rewrite (for improving performance, modularity and for general house cleaning) and the github branch doesn't reflect that right now.
Re: React Makes You Sad?
#65As a C and then a Ruby on Rails programmer, I never thought I would see the day that my main programming language was Javascript. But I find React such an enabling technology that I made the effort to learn Javascript properly, and am glad that I did. React itself is allowing me to write web applications faster and with less bugs, primarily because of the unidirectional information flow, but also because of the way i…
[deleted]
Re: React Makes You Sad?
#66Where's the branch for "sad because I know react, and have to change half a dozen files with dozens of lines of boilerplate each for each change request"? I know a few of those - folks who aren't beginners and who loved react to begin with, but are getting slowly disillusioned by the sheer volume of changes required to modify a data source or add a new widget. Dropping flux or changing bundlers won't change the core…
Would you mind expanding on this with some specific examples?
Re: React Makes You Sad?
#67We wanted to make it as easy as possible for new developers to jump into the React ecosystem without having to worry about how to set up WebPack, hook up redux, worry about styles etc… That's why we created https://github.com/TrueCar/gluestick which is a command line interface to help you get started. As Rails developers we missed commands like `rails new` or `rails generate` so we tried to make something similar for our front-end environment.
I highly recommend this blog post for anyone who is struggling with setting up React/Redux https://www.drivenbycode.com/getting-started-with-gluestick/
Re: React Makes You Sad?
#68Earlier quoted context omitted.
...where "other peoples mess" is based on battle-hardened production code from Facebook...
"battle-hardened", yet churns drastically every release? You and I have different ideas of what battle hardened means.
Can you please help me understand the issue by providing a specific example of how a new React release introduced churn in your project?
Re: React Makes You Sad?
#69All these libraries make me sad.
Re: React Makes You Sad?
#70Earlier quoted context omitted.
This is the weirdest argument I've ever heard against React, and, as someone who does a fair bit of React work, I try to pay attention to all those arguments.
It's certainly a weird phrasing of an argument. However, it seems reasonable that some programmers will not like the specific style of structure that react espouses. Specifically the top-down push of data through parent-child component relationships. Specifically, if you are working with a lot of third party components that are not react based, it can be hard (or a lot of boilerplate) to contain them within react app…
I've actually found it surprisingly easy to wrap 3rd party libraries in thin React components once you figure out the lifecycle methods and findDOMNode().