React - When Should I Use It?

-

     Since I've been learning React, it seems like companies everywhere are using it. Job postings left and right have a wide variety of back-end frameworks, with a React front-end. I think Blazor and ASP.NET are great, but React seems to be the more popular font-end tool (at least here in Utah). I figured I could compile a few of the reasons why I would want to work in React, and why I would want to avoid React. Keep in mind, most of this is my opinion based on my experience and a new developer.

    The Good

     React is widely used; Facebook built and maintains it, so there is guaranteed support until Facebook goes down, and even then there is a large enough community that it would still last at least a while longer. On top of that, React's ability to efficiently update the DOM gives it better performance than tools like Django. React apps feel responsive, and it shows in the developer experience. It doesn't have a lot of documentation you need to remember, and the responsiveness offers a quick feedback loop.

    Programming in React feels natural, my biggest issue when working in .NET is that there are a lot of black-boxes that we throw our code into. EFCore and ASP can be pretty confusing when you're learning, but React doesn't have hardly anything in it that you don't add yourself. I think the best part about React is probably the components, which are even better now with React hooks. Your whole project can be broken into isolated components that won't break each other if something goes wrong.

    The Bad

     Libraries, libraries, libraries. Many React projects (all npm projects really) end up depending on dozens of libraries, all of which need to be managed to ensure there are no version conflicts or other errors. On top of that, there might be several ways to do the same thing, and that results in a lot of decisions you need to make as soon as you start your project. This freedom is a benefit in some ways, and a downside in other ways.

    One of the issues I found while working on my React projects was that online documentation can be all over the place. Some docs are old, and outdated, while others relate to any of the dozens of React technologies (React Native, React Redux, etc.). It takes a little more patience and specificity to find answers to your questions.

    The Ugly

    JavaScript. JavaScript is ugly, it's wonky and weird. TypeScript is better, so it's great that React supports it, but if I never had to code in JavaScript again I would be quite happy.

Comments

Post a Comment

Popular posts from this blog

API's in C#

-
      There is a lot here to take screen shots, but the code is all on my GitHub here if you'd like to follow along with this post.       My wife teaches sixth grade, and lately I've been thinking about an application I could build her to help manager her classroom and motivate the students to improve on the skills they've been struggling with. The concept is to turn a classroom into a game of Dungeons & Dragons, except the skills are in things like math and reading. Students would answer questions instead of rolling dice, and can then add their skills to their results so they can earn experience and rewards. Originally I was going to build this in FastAPI but I thought .NET Core would be better for setting up models and working with a database.     I started by setting up my models in a shared class library project, and I added a Classroom class for tracking classes of students, a Student class for tracking the stats of students and a Logs class to keep track of how a
Read more

Using WebRTC to build a videophone in React and TypeScript

-
 Recently I had the opportunity to spend more time learning React, as well as Redux and a bit about WebRTC. I was prototyping a website that allows you to make video calls to other users, and I thought it was really cool how out-of-the-box WebRTC is. I also used TypeScript, even though I had some trouble in the past with React-TypeScript applications, and it went pretty well. There was some finicky things and it required me to learn the types of objects I had never used before, but overall I think it went pretty well.   The server is built with express, and uses socket.io to emit the web-rtc requests. There is no authentication or authorization, I was mainly focused on showing that I could make a video call.It uses Redux to handle state management, which was a bit tricky in TypeScript and felt like I was writing a lot of repeat code, but it got the job done better than it would have without it. Ultimately this project ended up being put on the backburner as my team turned to Flutter in
Read more

Reviewing WPF and MVVM

-
Image
 I've been working in WPF (Windows Presentation Foundation) a lot lately. WPF is a great way to build a Windows desktop application, it's been around for many years and is very mature compared to UWP (Universal Windows Platform) which is a similar tool for creating desktop applications. It's not the newest, shiniest tool but it is definitely a great tool to be aware of. A while back I built a simple WPF program that worked with a .NET function library that did very simple distance calculations, and I decided to review that before really getting into more advanced concepts. When the program runs, it looks like this:   It's nothing too fancy, but it will show travel time, rate of travel and distance traveled over time. It also allows an excel spreadsheet to be inputted and it will run many calculations and then update the spreadsheet. The layout here is primarily built using the XAML grid, a staple of any WPF application. The grid specifies how many rows and columns the g
Read more