Am I wrong in hating React JS?

45 点作者 eibrahim超过 8 年前

15 条评论

ggregoire超过 8 年前

To reply to your complaints:> I hate html in javascript. I hate JSX.At least it's just HTML and JavaScript.In my opinion it's better than learning a new messy templating DSL, i.e.<pre><code> <ul ng-if="::vm.items.length"> <li ng-class="::{ 'active': item.active }" ng-repeat="item in ::vm.items | orderBy: 'id' as ordered track by item.id" ng-click="item.active = !item.active"> {{::item.name}} </li> </ul> <select ng-options="item.subItem as item.label for item in ::vm.items2 track by item.id" ng-model="selected"></select> <div ng-include="selected.template.url" /> </code></pre> > I hate the lack of CLI. I hate the ridiculous amount of shit I have to do to simply get a project started.You can use the official Create React App CLI [1].> I hate the sheer amount of boilerplate code and the verbosity.How do you recreate the following component in Ember/Angular/Backbone/jQuery/FoobarJs with less boilerplate and verbosity?<pre><code> Header.js: import React from 'react'; import Icon from './Icon'; export default ({ icon, title, subTitle }) => ( <header> <h1><Icon name={icon} /> {title}</h1> {subTitle} </header> ); </code></pre> > I hate the lack of conventions — every project I look at looks different, every blog post looks different.React is just a library to build views, so there is not a single way to build your app in the React world. You can use Redux, MobX, Flux or whatever you want to manage your data. You can even do it in 100% raw vanilla JS. I think it's great.---[1] <a href="https://github.com/facebookincubator/create-react-app" rel="nofollow">https://github.com/facebookincubator/create-react-app</a>

评论 #12797808 未加载

评论 #12797607 未加载

carsongross超过 8 年前

Is React a fad?Yes.Is it here to stay?Yes.Should I get into it?Depends on what you need. If you are building a web application with complicated UX needs (protip: you probably aren't) and/or the team insists on React, you probably need React. If you want an easy time getting a job in the Bay Area right now, you probably need React. If you want to avoid having your comments downvoted on HN, you probably need React.So, it depends.

评论 #12798593 未加载

评论 #12797232 未加载

评论 #12799524 未加载

cbhl超过 8 年前

You are probably just experiencing change aversion, also known as "getting older". It's normal to have these feelings.There were people who programmed in assembly and hated compilers and C. There were people who programmed in C and hated Perl. There were people who programmed in Perl and hated PHP. There were people who programmed in PHP and hated Ruby. There were people who programmed in Ruby and hated that JavaScript suddenly was a "real" programming language.You'll probably be able to find work in your language/framework of choice for a long time, although as time progresses it will be less "hip startup" and more "enterprise" (look at C#/ASP.NET) and "banks" (look at COBOL).

评论 #12799659 未加载

acconrad超过 8 年前

You're not wrong in hating React, but it is a fad as much as no one wants to believe it. The reason I believe is because no matter how strong the framework, eventually it will be adopted (to some extent) into the native language (which is a good thing). Think about these frameworks:- jQuery- Coffeescript- Backboneat the time, if I had asked you if those were a fad, you'd think I was crazy. And yet, because of native language enhancements, none of those frameworks are really needed anymore. And I'm sure in 5 years React, Angular, Vue, Ember...you name it, will also likely be a thing of the past.The important thing that I've learned in my (so far very short) career is that it's always best to know the language first, and the framework second. Frameworks come and go, but the language is permanent. By knowing the language really well, it's strengths and weaknesses, it enables you to determine when a framework is helpful...and more importantly, when a framework is a hindrance.As an anecdotal example, I had a client that was using a React boilerplate on NPM to do a Foursquare API request. React is like, 50k lines uncompressed? To do that? I was able to replace it with 22 lines of vanilla JS. If you don't know the base language, it's often easier to simply think in the framework and create a bloated environment for very basic things rather than just use what the language gives you. It's faster, it's cleaner, it's more widely supported in browsers, has a larger community, and is more defensible to use the base language than a framework, until the framework does more work to help you than harm you.So my advice would be, if you're thinking about using React or Angular, think about why you need it. Are you doing heavy lifting on the front-end, like interactive graphics or a dashboard? Sure, those are probably pretty good choices. If not, and you're simply trying to make the front-end more RESTful, with some easier reasoning about your applications, you could probably get away with a lighter framework like Mithril, Elm, or another lightweight framework.

评论 #12798108 未加载

mariusc23超过 8 年前

I wasn't a huge fan of JSX until I saw the template errors in Angular 2. Not trying to bash on the rest of Angular 2, but it really made me appreciate how JSX points out the exact syntax error at compile time. Pretty much all template based frameworks have the same problem.It took a while for React to "click" for me, but that was mostly because of transitioning from MVC to Redux. I highly recommend learning pure React first. Build a project with that first, even if it seems like you're writing a lot of code.

zghst超过 8 年前

I recall a few years back I hated Ember JS and kept trying to get into it and hating it then for some reason the 3rd time I did, it stuck and I LOVED IT.Seems like you're already obstinant and opposed to tech from it's perceived novelty and new age, rather than trying to understand the problems its trying to solve.

jameskilton超过 8 年前

What may help is to change your perspective, and to change your word choice.It's not hate. It's definitely not hate. You don't like React, and that's perfectly fine. "Hate" has some very specific, very negative connotations that make almost impossible to have a regular conversation. One of my mentors uses the term "stop words". Hate is on that list of words that, when used, stop the conversation in its tracks.It's ok to not like things. It's perfectly OK to not like Javascript frameworks. There's a ton of them, or you can write your own if you feel that's necessary.But please, can we stop throwing around the word "hate"? It does nobody any good and only furthers the problems of ego and exclusivity prevalent in our industry.

评论 #12797532 未加载

formula1超过 8 年前

The reasons why you should like react- forces you into an object oriented paradigm with constructors/destructors- mutation from external sources and internal sources results in a single function being run to refresh the output.- inline html/xml is your freind. You can see easily how a ui is structured rather than parsing a 300 line file to see what gets created, destroyed, appended, prepended anD etc- all jsx results in is a "patch". This "patch" is then compiled into components (which also result in a "patch") or html elements/text/null values. This makes reasoning about the application simpler since a "controller" component may not care about updating canvas info. But the "canvas" component certainly does

评论 #12798792 未加载

评论 #12799914 未加载

xiamx超过 8 年前

May be you should try it more than three times. Like you've experienced with ember and vim, the epiphany comes all of a sudden

评论 #12797246 未加载

raquo超过 8 年前

> I hate html in javascript. I hate JSX.How about hyperscript? Functionally equivalent to JSX but it's pure JS, with no XML syntax.<pre><code> header( h1(Icon({name: icon}, [title]), p(subTitle) ) </code></pre> I don't think you can make an argument against building the DOM in JS (instead of using some random DSL to parse HTML template strings) without falling into the fallacy that JS === logic and HTML === presentation. But, you don't seem to be making arguments.

gremlinsinc超过 8 年前

Then don't use it, imho Elm is way better, and the way they write html in elm is a lot more pleasing and less ugly than jsx. I'd recommend taking a look. It also compiles to js and has better performance.

评论 #12798667 未加载

zilchers超过 8 年前

I'm with you on the embedded HTML in JavaScript files. There's a reason everyone went nuts for MVC, the seperation of UI code (in my opinion) just makes your life as a developer easier.

评论 #12800101 未加载

评论 #12798072 未加载

shahmeern超过 8 年前

I think that enjoying working in a framework/library is very much a function of how familiar one is with the framework/library.It might be worth giving React that 3rd try.

busterarm超过 8 年前

I kind of feel this way about React, but I feel even more strongly this way about Ember.For one thing, I haven't been to a single React site that isn't an absolute CPU hog. Facebook is the worst for this.Besides that though, I feel like it's still some intermediate step before we have something better.I'm bullish on Elm though. For now, plain vanilla (but mostly functional) JS works fine for me and occasionally I'll throw in Backbone/Marionette where appropriate. Maybe that's too boring for people, but I'm too busy being happy with a stable stack and making money to care.

fractalf超过 8 年前

Best thing I've read about react js ever! +1 Every time some person I talk to mention react, part of me want to vomit.