NetBeans vs. React

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
NetBeans
Score 7.8 out of 10
N/A
NetBeans is a free and open source platform and integrated development environment (IDE).N/A
React
Score 9.3 out of 10
N/A
React is a JavaScript library for building user interfaces. React enables users to create interactive UIs. Design simple views for each state in an application, and React will update and render just the right components when data changes. React is available free and open source under the MIT license.N/A
Pricing
NetBeansReact
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
NetBeansReact
Free Trial
NoNo
Free/Freemium Version
NoNo
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeNo setup fee
Additional Details
More Pricing Information
Community Pulse
NetBeansReact
Best Alternatives
NetBeansReact
Small Businesses
PyCharm
PyCharm
Score 9.1 out of 10

No answers on this topic

Medium-sized Companies
PyCharm
PyCharm
Score 9.1 out of 10

No answers on this topic

Enterprises
PyCharm
PyCharm
Score 9.1 out of 10

No answers on this topic

All AlternativesView all alternativesView all alternatives
User Ratings
NetBeansReact
Likelihood to Recommend
7.8
(22 ratings)
9.9
(14 ratings)
Usability
9.0
(2 ratings)
10.0
(3 ratings)
Support Rating
8.5
(4 ratings)
10.0
(3 ratings)
User Testimonials
NetBeansReact
Likelihood to Recommend
Open Source
NetBeans is extremely user friendly and easy to start developing complex applications. Adding and configuring external libraries is much simpler than in Eclipse. It is highly cost effective and most of the latest framework based libraries required are automatically downloaded to the projects. The overall tool is also light weight and consumes less memory as compared to other competitor tools.
Read full review
Open Source
React is a JavaScript user interface construction library that works well for:
  • Developing web apps with dynamic and complicated user interfaces.
  • creating reusable UI elements that may be used in other applications.
  • creating single-page applications with dynamic content updates that don't require a page reload.
  • The Virtual DOM's effective updating mechanism allows it to handle large volumes of data updates.
React, on the other hand, might be less suitable for:
  • Websites that are simple, stagnant, and have no interaction. Other libraries or simple HTML, CSS, and JavaScript may be a better fit in such circumstances.
  • Web sockets may be a better choice for applications that need real-time updates, such as chat or gaming apps.
  • When creating mobile apps, React Native is a better option.
  • Server side rendering only, as React is designed to run on the client side.
Read full review
Pros
Open Source
  • Debugging - Save time hunting down errors by stepping through the code to find the root of a problem.
  • Refactoring - Easily rename classes and variables or make other structural changes using built-in refactoring tools.
  • Service management - NetBeans integrates seamlessly with web application servers like Tomcat and GlassFish.
  • Source control - Works well with Git and other version control tools.
Read full review
Open Source
  • React is fantastic for building performant user interfaces. Our web app is snappy and great for our customers.
  • React has the philosophy of doing one thing and doing it well which is the view layer of the application. This makes it incredibly intuitive and flexible for developers to use.
  • React has lead the way in being able to write modular and structured code. It is a drastic improvement since the days of spaghetti jQuery code.
  • React has an unmatched community. The amount of tools and libraries available is fantastic, and there plenty of solutions available online for common problems.
Read full review
Cons
Open Source
  • NetBeans [should] work smoothly with systems having less RAM. Systems with less RAM face trouble with NetBeans.
  • File open history also requires improvement. Once NetBeans is restarted, all files are closed automatically and there is no shortcut to open last opened files.
Read full review
Open Source
  • Debugging React is challenging. Bugs in react code generate stack traces internal to React and it is often totally unclear how it relates to the code you actually wrote.
  • Relating your React elements to corresponding DOM elements is difficult. The intentional separation of virtual and actual DOM also makes it difficult to map the elements to the structures in the DOM. This is partially ameliorated by the use of the React dev tool, which provides a DOM-like view of the React elements, but the tool still does not provide a direct correspondence with the DOM that is often necessary to figure out why something isn't right.
  • Because JSX is React-specific and not a language feature, a special compilation process is necessary to convert JSX code to normal JS. Coming from a C++ background, compiling things doesn't bother me, but many JS developers are used to a less structured development.
Read full review
Usability
Open Source
Netbeans enhances my coding work, shows me where I have errors and helps find variable instances. I would be lost without find/replace in projects functionality as I use projects as templates for new projects. Occasionally the code hints aggravate me, but I understand that it is actually making me a better coder, working to get the 'green light' of a clean file with no errors or clumsy code.
Read full review
Open Source
React is just a bit of a different animal. I was avoiding it for the longest time. I thought for sure I would land on Vue or something else with a more approachable and familiar appearance. But after taking an online course in React, I started realize what people were raving about (and complaining about) and decided to implement it at our office for one of our products.
Read full review
Support Rating
Open Source
NetBeans has a very strong user community. We can find solutions here for almost all the problems we face. In addition, we can forward NetBeans Support teams the problems we cannot solve. We can get quick feedback from the support teams, but I generally try to solve my problems by following the forums.
Read full review
Open Source
Since it's open-source and very popular, the community support for React and related tools and libraries is excellent. There are a lot of people using the same tools, and so issues tend to get fixed quickly and "recipes" are easy to come by. And since it's backed by Facebook, they have a dedicated engineering team working on the progression of React.
Read full review
Alternatives Considered
Open Source
It works very smoothly as compared to other tools . The problem of restarting and reimporting the projects is not in the netbeans IDE . The front end development features are good . Netbeans connector is one of the best thing which enables us to deeply integrate netbeans IDE with google chrome browser
Read full review
Open Source
While this is a widely contested debate with various blog posts and benchmarks all over the place, its really a personal choice to determine what works for the team. Coming from a Angular 1.x background, I decided to try a new framework when Angular 2.x was announced and at that time React is gaining popularity and Vue hasn't taken off yet. Compared to Angular 1.x and Vue (hybrid of React and Angular) that split the logic from the html templates, I loved the way React breaks code into components using the jsx syntax. In my mind, this allows for cleaner components and easier maintenance
Read full review
Return on Investment
Open Source
  • By working on Netbeans I just learned one more tool and can teach others about it. One should learn every tool so that it might help someday if another editor is not available and you have to use different software for your work.
  • Compiling code became easy as it is not a feature of normal text editors. Only IDE can do this.
Read full review
Open Source
  • Our web applications now run much faster because the whole page doesn't reload
  • We spend less time developing UI components because a lot of them are readily available on NPM
  • We don't have to optimize apps for multiple browsers since React natively supports it.
Read full review
ScreenShots