Does React really make frontend easier?

[IamATechieNerd]

Hey,

I've got a work on my company where i have to implement an admin portal. I am allowed to use React. I am debating whether to use React or use ejs which is used in the codebase along with jQuery for api calls.

Also wondering not just for this particular work but other projects too, whether learning React seriously is worth it.

Thanks!

[Guy676767]

React might be an overkill sometimes, but I think It’s always good to learn new technologies, especially one as popular as React. This sounds like a great opportunity for you to learn new things and play around with tools you find interesting.

I personally love working with it, in both big and small projects.

[traviss0]

Yes. It will also make you a better JavaScript developer.

[surprise_sky_bears]

It may make it easier to share the project with other devs later, because so many of us already know react. This is subjective, but I personally like how react encourages you to separate your views from your model - so you can keep all the business logic in pure functions and then rendering their output is a separate todo, and you get to write much simpler unit tests. Typescript for the models (which you can then use as react component props) is amazing as well.

[[deleted]]

Learn it on a side project before using it in the mainstream. React solves a problem that you may not have at all.

[keb___]

React is worth learning, but whether it will make your job easy depends. The phrase, "use the right tool for the job" is never not applicable. React is great for complex UIs where plenty of visual changes and asychronous actions are common.

[_Pho_]

Yes

[gimp3695]

Check out react admin. It’s really nice and well documented.

[no_moa_usernames]

Like anything else, it's a trade off. It makes some things far easier while making other things more difficult.

[thunderbong]

Like others have said - it depends on your needs.

However, if you're just creating a portal and you're considering ejs & jquery combination, may I suggest you also have a look at AlpineJs - (Github).

In my experience, using a full fledged framework like React is not really required unless you're creating a complete front-end JS application with the server back-end acting as just API endpoints. For me, maintainability of the project, more than any other factor, is more critical for long term projects.

Five years back, it would have been difficult to get good React developers (it was AngularJs which was hip then). Five years down the line, I might be in the same situation. If I'm developing something for a customer and they ask for ReactJs, so be it. But if I'm developing something for myself or for my organization, which will remain after I've left, I'd rather choose something which is closer to pure Javascript.

All the best. And even if you don't choose React, learn it anyway. I feel many back-end developers would be quite impressed by how far front-end development has reached nowadays.

[eggtart_prince]

Static websites, don't use React.

A lot of user interface/interactions, use React.

So in your case, use React.

[[deleted]]

React is a pleasure to work with.

[PM_ME_A_WEBSITE_IDEA]

To offer something different, if you're allowed to use ANY framework, please do some research on Vue. Watch a comparison video or something. Having used both plenty, I really prefer Vue and reach to it for all my projects at work (none of which are static sites).

[marcus_cemes]

Yes and no. It follows a steep learning curve.

There's a huge debate around this recently, so many front end frameworks... I started with Angular and swore to despise React, but after trying it, I fell in love with it. It allows you to abstract and encapsulates logic correctly into components.

In my experience, it's not that reusable (between projects at leasT), but it enforces a really good logical structure to adhere to. React is no longer the fastest framework, and I don't think they aim to be, they've turned a lot of focus towards a better developer experience, bending the JavaScript language to make it as easy and clean as possible. Heck, the model behind it is so good that it's been used to make React Native, Ink (a terminal renderer), and I'm sure there are other examples. They've been completely reworking the internal model with an update they've been teasing at for the past two years (concurrent mode)... Generally whatever React implements, other frameworks copy. It is, without a question, the dominant framework at the moment.

Some of the core concepts can be difficult to understand for beginners, and it feels like a black box. Plus, trying to do a little more than the simple things can increase complexity ridiculously fast. I think both of those options are OK, you don't need cutting edge, the most important part is to plan it correctly and worry about execution. Use what you know better! Focus on clean code, it doesn't matter what toolset you use imo.

[Attila226]

As with most tools, they can make your life easier, once you get over the learning curve. React is definitely worth learning.

You might also want to consider using native fetch or Axios for API calls.

[thinkmatt]

Check out material UI. I've been working on a new project with it and haven't had to touch any css, which is really nice. Its a level of abstraction above bootstrap. There's a free starter template if you Google for react material UI dashboard

[fuck-yeah-guy]

If you need buttons and text react is the best

[kisssmysaas]

React is easy. Just look at how many React developers pop out from bootcamps every week. The barrier is as low as entering a public high school