Navigation Menu

Skip to content

Instantly share code, notes, and snippets.

@gnomeontherun

gnomeontherun/components-whats-in-a-name.md

Last active September 18, 2015 18:41
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save gnomeontherun/6e7131ef2f06bbdbf6a9 to your computer and use it in GitHub Desktop.
Save gnomeontherun/6e7131ef2f06bbdbf6a9 to your computer and use it in GitHub Desktop.
Download ZIP
Web Components: What's in a name?
Raw
components-whats-in-a-name.md

The term "component" is overloaded in frontend development. There are Web Components, Angular Components, Ember Components, and React Components. What makes them different? How do these all behave?

Examine the principles behind these various types of components and how they address the concepts of reusability, modularity, and encapsulation. Under the hood, these different approaches often solve the same problems, but there are tradeoffs.

You'll see a set of examples built with Web Components, Angular, Ember, and React that demonstrate how the different approaches work and expose some of the limitations they have.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment