- CTO of Levanto Financial, where I work on tools to help people work toward their financial goals.
- Founder of Modern Web UI, a Silicon Valley developer community focused on sharing ideas between framework communities.
- Formerly: UI Architect of Yahoo Ads & Data, where I led development of the company’s ad platform, and over a dozen other related products.
- Instructor on Frontendmasters.com, video courses are soon coming to Pluralsight and O’reilly.
- Speaker and startup advisor, focusing on opinionated web frameworks and modern web development.
- Twitter, GitHub
All of the tools we rely on like Angular 2, React, Ember, Polymer, etc... are, essentially, shims and hacks that we make use of while we wait for things like the W3C Web Component spec to be completed and implemented in browsers. As it becomes more feasible to build on the standards instead of a framework, it'll become useful for developers to have awareness of what those standards are, what’s missing from the official spec, and how well of a job our favorite libraries do with establishing alignment.
We’ll take a close look at the W3C component spec, and compare it to the concept of a Component in the React.js library, the and the Ember.js 2 and Angular 2 frameworks. We’ll try to do a few things using native web components, involving rendering and styling an encapsulated piece of interactive UI. Along the way, we will highlight the things that we’re waiting in the W3C spec. We'll be left with a clear roadmap of when we can start decoupling our apps from a specific third party tool and rely on “Native Web Components” in production.