+1.
i am paying this tax tinkering with reactjs getting it to do stuff which is very trivial with normal html/js world
ReactJS is a tax Facebook levies on startup web development
11–20 of 37 posts
Re: ReactJS is a tax Facebook levies on startup web development
#12Especially when all you're building is a basic CRUD form.
Not knowing the nature of author's project, I think the issue is not so much about "levied taxes" but back to the wisdom of choosing the right tools for the problem at hand.
Re: ReactJS is a tax Facebook levies on startup web development
#13Yeah, no. At least not any more than the same holds true for Angular, Ember, etc. And thinking it's some ingenious evil plot is a bit silly.
Re: ReactJS is a tax Facebook levies on startup web development
#14This is silly. Facebook isn't forcing anyone to use React. People use it because it works better than the status quo.
>The component philosophy of React does offer some organizational benefits, especially for working in a team, but it’s nothing that couldn’t be replicated by some simple coding conventions.
If it's so simple to organize code why do many vanilla js codebases quickly devolve into spaghetti? It may be simple for the author, but not the average dev. Hell, it may not even be simple for the author if the author was placed in charge of a team of average devs! Just because something is easy technically doesn't mean it is easy politically. You can be "right" about something but still struggle to get others to play along. React predefines the rules and it is validated by a major tech company so people are apt to play along.
Re: ReactJS is a tax Facebook levies on startup web development
#15This article is disappointingly short.
While I agree that React stuff can be done with vanilla HTML and JS for me at least it has been a dramatic improvement in code quality and productivity. And this coming from someone who refused to use jQuery for Ajax when it first came out, I don't jump on bandwagons lightly.
I also haven't seen performance issues assuming you remember to turn off debug in production. But that is not to say there isn't any.
But everyone has their own experiences.
I will say, I don't know if you can call it a tax when no one is forcing your startup to use it.
Re: ReactJS is a tax Facebook levies on startup web development
#16React is absolutely overkill for many, many web applications.
The temptation to over-engineering has been seen again and again, yet the industry continues to fall for it.
I think a lot of it boils down to the cult of the new/a fear of being left behind and, perhaps more pernicious, fear of being perceived as 'not smart enough' to deal with the complexity of these tools.
Re: ReactJS is a tax Facebook levies on startup web development
#17Components is the main benefit of React. It forces you to think modularly, which can be very difficult at first.
Re: ReactJS is a tax Facebook levies on startup web development
#18I do react professionally. EVERY DAY. And yes I agree with you to a large extent. I just don't think it's react specifically. Take for instance, building an address form. In the year 2016 this has never been more difficult. What used to be two hours of html/css/jquery, has been turned into a nightmare of our own design. React and other heavy hitters do serve a purpose, but I think it's fair to say that things are harder now than ever.
We live in a world where many js devs only know js, this wasn't true 10 or even 5 years ago.
Re: ReactJS is a tax Facebook levies on startup web development
#19I've been using React for just about everything front-end wise for the past year. I don't think it's particularly hindered me, really. Sure, it was a learning curve, as was Redux, but now I understand those concepts better, my process is, I clone a 'react starter pack' from git, which has all of the build set-up I need, webpack, sass, ES6 etc, etc. And that's really it, I find it quicker to develop in React and Redux…
I'm quite surprised seeing quite many comments telling how they use React "for everything".
Isn't React just a small[1] library that essentially does only one single thing? (And does it well) Takes a component definition, a state object, and then renders (and maintains) the component as a DOM structure?
Unless I was looking into some other React that everyone's talking about, or I've had my eyes looking somewhere else and missed something giant - I'm sure it is. Then, how come everyone's doing everything with what's just an evolution of the templating libraries? I mean, even a simplest CRUD front-end webapp isn't only about the UI.
Not trolling, I really don't get it.
____
[1] Well, technically it's not really small, because it does not of stuff under the hood to implement those virtual DOM and make things efficient. But it's end-user (=web developer who isn't hacking on React internals) functionality isn't wide-scoped. It's a library after all, not Angular or another we-do-it-all framework.
Re: ReactJS is a tax Facebook levies on startup web development
#20One of the most important skills in web engineering is navigating an ecosystem of tools that grew more complex to use than the problems they originally aimed to solve. And ignoring those tools, identifying and adopting only the ones that are exceptions to the rule.
While I sympathize that React ended up this way effectively, I don't believe it was the premeditated intent. It happens often enough without malicious intent that Occam's razor suggests this is only another non-malicious case.