JavaScript is a great language. It is flexible, extensible, and very expressive. Such qualities also lend it to being used in ways it should not be. These qualities translate into errors in coding when using many JavaScript libraries, including React and MobX.
MobX is yet another entry into the state management space for user interface (UI) applications. Its biggest competitor is Redux (especially in the React space).
Why do some developers avoid two-way data binding, while others love it? How does two-way data binding factor into the component-driven development revolution?
While the dream of Web Components as an implemented standard has not yet been realized, many attempts have been made to bring the concepts behind the standard to developers now through various coding patterns and technical wizardry.
In this post, we will continue to explore properties that can be configured with the new class syntax and made available on objects that are instantiated. In particular, we will explore function properties, accessor properties, and static properties.
ES2015 offers many helpful new features and cleaner syntax for existing features. One example of this cleaner syntax is the class keyword, as well as improved syntax for using prototype inheritance in JavaScript applications.
