JavaScript for Line of Business Applications

Just as for many front-end developers, our stack used to consist of HTML and jQuery. We would do AJAX requests to our backend, render the new chunk of UI on JavaScript and insert it into the DOM. User actions were tracked by binding events and callbacks to each of the elements. And don’t take me wrong: this is just fine for most applications.

However, when an application grows considerably, a couple of issues start being more frequent than expected: you forget to update all places where a value is displayed in the UI, no events are bound to the content added by AJAX, just to name some — this list can be very long. These are signs that your code is not maintainable, especially when developing together with a team. Using a front-end framework provides a formal way to write collaborative code that you can read, write and update.

The main performance hotspot in React applications is redundant processing and DOM diffing in components. In order to avoid this return false fromshouldComponentUpdate as high up in your application as you can.

To facilitate this:

1. Make shouldComponentUpdate checks fast
2. Make shouldComponentUpdate checks easy

There’s this thing going on in the Front-End Development community where everybody wants to re-write their applications to use React. Sorry…

Redux & React are currently mainstream technologies in front-end. Every self-respecting front-end developer knows this fact and tries to dive into them to understand what they are and how to deal with them. Because it seems really clear that the future web applications are all about this sweet couple.

The problem is that the process of changing developer’s mind to start thinking in React & Redux way isn’t actually smooth. Frameworks we used to apply (Backbone, Angular, jQuery, etc.) work in drastically another way, so we need some time to switch.

Obviously, when we hear about React & Redux bunch, we begin to puzzle out exactly those two words. And that’s right for a start. React serves as the view layer, Redux serves as the data one…

Unlike most front-end web frameworks, React's aim is to solve the various challenges of building user interfaces that rely on changing data. Although React is a simple JavaScript library and is easy to get started with, it is still possible to misuse it in ways that deny the web app from reaping the benefits that React has to offer. In this article, Toptal engineer Ivan Rogic demonstrates the synergy of React, Redux and Immutable.js, and shows how these libraries together can solve many performance issues that are often encountered in large web applications.

MERN is a scaffolding tool which makes it easy to build isomorphic apps using Mongo, Express, React and NodeJS. It minimizes the setup time and gets you up to speed using proven technologies.

This guide goes through setting up, running and exploring the ultimate JavaScript Stack du jour:

• TypeScript - Superset of JavaScript with optional typing, advanced language features and down-level ES5 support
• JSPM - JavaScript Package Manager supporting SystemJS modules and multiple npm and GitHub repositories
• TSD - Package manager to search and install TypeScript definition files
• React - Simple, high-performance JavaScript UI Framework utilizing a Virtual DOM and Reactive Data flows
• Redux - Predictable state manager for JavaScript Apps

Providing a great base for the development of large-scale, JavaScript Apps that's further enhanced by a great development experience within Visual Studio.

Redux has emerged as the preeminent framework for building React-based web applications. It perfectly complements React's declarative views with a straightforward and elegant architecture that brings some of the best ideas of software engineering theory (immutable global state, functional programming, Event Sourcing, CQRS, etc.) into the web development mainstream. "There

GigaGrid - Massively performant, multi-layered React.js table widget Written in TypeScript

High level overview of all the tools available for styling React components, and how they fit together. Covers PostCSS, Sass, BEM, CSS Modules, Autoprefixer, cssnext, and more.

With React Storybook, you can develop and design UI components outside your app in an isolated environment. It will change how you develop UI components.

State management within Angular started out as a single celled organism if you will in the form of a single controller managing all the state for the application. If this is a single page application, one controller makes sense right? We emerged out of the ice age by starting to group our views and controllers into smaller, self-contained units either within a directive or a route. This was a vast improvement, but there was still the problem of managing complex state within our applications. It was not uncommon for us to have bits and pieces of state strewn across our application tucked inside of controllers, services, routes, directives, and occasionally, in our templates. Mutable state in itself is not inherently evil but shared mutable state is a recipe for disaster.