Book Image

Reactive Programming with JavaScript

By : Jonathan Hayward
Book Image

Reactive Programming with JavaScript

By: Jonathan Hayward

Overview of this book

<p>Reactive programming is carried out using the building blocks of functional programming. JavaScript libraries such as ReactJS are used for front-end web development that is both competent and powerful. ReactJS is intensively being used to develop webapps for Facebook.</p> <p>This title is among the first of those addressing how everyday programmers can take advantage of reactive programming without having an extremely heavy mathematical background. It starts with the basics a front-end developer can easily connect with, while also covering the basics of functional programming. Then it goes on to explain non-functional reactive programming with the help of a live example. After that it gives a theoretical overview of reactive programming supported by functional programming. Tools to make functional programming easier like Bacon.js, a library like jQuery, are also covered. Finally, it finishes with building one small and one larger front-end project.</p>
Table of Contents (20 chapters)
Reactive Programming with JavaScript
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
9
Demonstrating Functional Reactive Programming in JavaScript with a Live Example Part II – A To-do List
Index

The Big-Coffee Notation


Steve Luscher, a ReactJS guru and enthusiast outside of Facebook who was subsequently hired by Facebook, has talked about the Big-Coffee Notation in a video on React. The basic insight is that instead of using only the big-O notation for runtime complexity (how long the runtime slows down as a function of the rough size of a problem, or occasionally other dimensions, such as memory usage), we should have a Big-Coffee Notation for what the demands scale for the poor developer, who has to keep things in their own poor, caffeinated brain.

Gerald Weinberg's classic book The Psychology of Computer Programming works out a basic insight at admirable length. The core insight is that programmers programming computers is not just an activity that involves computers. It's also an activity that involves people, and we would do well to treat it as such. Perhaps we should also know the limits of computers, but the human side of this is not, in any sense, trivial. Weinberg may have...