The “Bug-O” Notation

The “Bug-O” Notation

For example, consider this code that manually updates the DOM over time with imperative operations like and and no clear structure:

The problem with this code isn’t that it’s “ugly”. where n is the number of code segments touching the DOM. The component abstraction enforces boundaries so that you know no other code on the page could mess with its DOM or state.

Source: overreacted.io