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.
Am I wrong in hating React JS?
21–30 of 40 posts
Re: Am I wrong in hating React JS?
#22I 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.
Re: Am I wrong in hating React JS?
#23Is 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…
> protip: you probably aren't
Citation needed. HN has this really strange assumption that everyone who talks about web technology is working on Wordpress sites or implements TodoMVC for a living.
Re: Am I wrong in hating React JS?
#24Then 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.
I love Elm too, but Elm's biggest problem is Elm. It's hard to justify picking anything other than Javascript if other people are going to be touching the codebase.
Re: Am I wrong in hating React JS?
#25The 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 res…
I respectfully disagree. You don't need constructors and certainly not destructors (really not sure what you mean by this in the context of React, can you elaborate) and these are not really the main OO concepts. Polymorphism, inheritance are, but you don't refer to these?
There is no inline XML, and I'm not aware of any other popular (or otherwise) React alternatives where you use long files which create, destroy, append and prepend DOM elements?
I'm also not sure what you mean by patch, or what the specific benefit you're highlighting here is - just modularity? You can do that with any framework, it doesn't seem unique to React - at all?
Re: Am I wrong in hating React JS?
#26The 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 res…
I respectfully disagree. You don't need constructors and certainly not destructors (really not sure what you mean by this in the context of React, can you elaborate) and these are not really the main OO concepts. Polymorphism, inheritance are, but you don't refer to these? There is no inline XML, and I'm not aware of any other popular (or otherwise) React alternatives where you use long files which create, destroy, a…
Component will mount/component did mount is effectively construction. Component will unmount is effectively destruction. Apparently them changing the names makes you believe thats not what it is
Polymorphism and inheritance can be implemented if you wanted. Mixins were used for a while.
Xml is react native and all other alternative rendering that use jsx syntax and a form of react
React alternatives where you create/destroy/append/prepend would be the DOM.
Patching is interesting in that the inline html isnt actually html until the end of the render loop. I dont remember seeing that anywhere else to be honest. It seems more similar to transforms like in node streams.
Re: Am I wrong in hating React JS?
#27Is 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…
Whats the threshold for "complicated UX needs"? I'd think for all but the very most basic bootstrap landing page (IE, if any of the value of your business other than a sales sheet is in your webapp) you'd want to use decent tools.
Re: Am I wrong in hating React JS?
#28Best thing I've read about react js ever! +1
Every time some person I talk to mention react, part of me want to vomit.
Re: Am I wrong in hating React JS?
#29Is 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…
> protip: you probably aren't Citation needed. HN has this really strange assumption that everyone who talks about web technology is working on Wordpress sites or implements TodoMVC for a living.
It's a 3.5 year old framework. Unless your career is "technical cofounder" with 6 month intervals, you probably don't get to pick your stack. People that have up and chosen React for their professional platform and have their company succeed aren't going to be all that common[0]. Within those that have, people who have used it for long enough (and large enough) to burn their hand on the stove are few and far between. Remember when Angular was the golden child and could do no wrong? It's 6 years old now, and took a while before the fandom died down and you could actually find the practical criticism.
I think the assumption that everyone does a 'Todo' is definitely a poor one, but I feel like 90% of the React articles are by people that have used it for 6 months at most, company blogs included. Glancing at the angular builtwith stats[1], they had 600/10k within 4 years. 3.5 years into React and it hasn't broken 100. While these numbers don't directly translate into "complex UI", they are still indicative of long term usage, going back to my hand-on-stove comment.
Re: Am I wrong in hating React JS?
#30You 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 JavaScr…
> also known as "getting older"
I disagree with that. It's not about age, it's about experience. React is essentially reimplementing ideas from the past on a new platform. I think it's more skepticism that React is 'it' as the next big UI view layer. The tolerance for bull goes down as you age, and sometimes the next big thing is just a different way of polishing the same ideas from 20 or 30 years ago.