Choosing a web component Model

  1. Abstract the Platform. Avoid HTML, CSS and DOM as much as possible. Write everything in JavaScript. Then use all of the wonderful features of JavaScript, mentioned above, to componentize your app. This is the approach championed by Facebook, React and it’s ilk. This is a very successful approach and is widely used today.
  2. Embrace the Platform. Utilize the recently added componentization features of the web platform itself. This is what the W3C Web Components spec is all about. Polymer (and Angular 2 ??) is based upon Web Components.
  • Ecosystem and supply of high quality components
  • Ease of creating a component
  • MVC-ish
  • Performance
  • Architecture and maintainability
  • Templates and data binding
  • External DSLs
  • Legacy integration
  • Interoperability
  • CSS and HTML Encapsulation
  • Theming

MVC-ish

Conclusion

--

--

--

Developer, Trainer, Coach | Kotlin | React | Flutter | https://smart-soft.com

Love podcasts or audiobooks? Learn on the go with our new app.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
David Ford

David Ford

Developer, Trainer, Coach | Kotlin | React | Flutter | https://smart-soft.com

More from Medium

Understanding Components in ReactJS(props and state discussed, with event handling)

Controlled vs Uncontrolled Component

Package React components for npm [1/3]

Screenshot of createapp.dev interface with React and Babel selected, generating a basic webpack.config.js

Getting Started with Typescript, Why Typescript over JavaScript