Why You Should Consider ReactJS for Your Web Application?

Why You Should Consider #ReactJS for Your #WebApplication? 

#IT #Techtalk

  • Yes, we are talking about ReactJS – the JavaScript library which is the hot favorite of developers and is climbing the popularity charts every day.
  • Managing system updates is very easy with ReactJS because every change does not necessarily affect each component in the system.
  • Developers using ReactJS have free access to a variety of useful applications and tools from the community at large.
  • Apart from these, there are numerous other examples such as Uber, Salesforce, KISSmetrics, Tesla, Scribd, Reddit, Periscope and many more which have leveraged the power of ReactJS to build world-class interactive web applications.
  • If you are looking to develop SEO-friendly, interactive web applications with great UI and expect your application to handle heavy traffic, it’s time to migrate to ReactJS.

According to the 2016 StackOverflow developer survey, React.Js’s popularity had recently increased by over 300%.What is making ReactJS so popular? Let’s take a look why you should consider ReactJS for your web application?
Continue reading “Why You Should Consider ReactJS for Your Web Application?”

React + D3.js: Balancing Performance & Developer Experience

#ReactJS + D3.js: Balancing performance & developer experience  #JavaScript

  • The idea is still to use D3’s helpers and JSX to render SVG elements, except that now the elements rendered by React are rendered without attributes, and D3 is used to add their attributes.
  • Each of these methods can use typical D3 code to position, style, and transition elements.There are some caveats to this approach:As declared in the post introducing this idea, exit() transitions are not supported without bringing in React’s TransitionGroup.Since React does not keep track of attributes, we have to manually implement state comparison to detect when the component should update in order to call the update() method performing D3 transitions.
  • I believe this is due to the need to split the code according to the line of ownership between React and D3, instead of splitting it into logical units.Solution 3 — Feed D3 a fake DOM that renders to stateThis is the solution I found the most elegant so far, and it is what powers the demo at the beginning of this post.
  • That fake DOM is manipulated by D3 and then automatically rendered as React elements stored into the component’s state where React can pick up changes and kick-off an update, including lifecycle methods and reconciliation as you would expect.I found this approach elegant because both D3 and React are used without alienation.Except for feeding the faux DOM node to D3 instead of using a selector as you normally would, vanilla D3 code can be used.
  • Hence, you get to enjoy the typical render performance of React components.SVG elements are automatically transformed into React elements and are inspectable in the devtools.The implementation is compatible with server-side rendering, so you get isomorphic charts at no cost.Overall, this solution has restored my faith is having a great DX when using D3 visualizations in React components, while making the most out of React’s render performance.

Let’s put it out there, I love dashboards. I find the way they help you gain a rapid understanding out of complex information really interesting. I have written real-time data visualisations in the…
Continue reading “React + D3.js: Balancing Performance & Developer Experience”