Goals

Personal goals (reasons I started working on a library)

Personal goals may clash with value- or community goals, as for instance backwards compatibility may not be a very good idea.

• Should work with generic WCs and be agnostic to what WC library is used
• Should perform two-way binding with properties of WCs
• Should bind to events from WCs
• Doesn't have to bind with attributes. It's the responsibility of the WC library to reflect the properties... But maybe this could be a feature?
• Should have a templating-system (at least a foreach) that works with WCs
• Backwards compatible with Knockout views and viewmodels
• IE11 compatibility

Added value goals

• Better syntax
  • Punches style?
  • Decoupling or loosely coupling the viewmodel from the library: getter/setter encapsulation? (even with decorations, if used with Typescript as in https://github.com/gnaeus/knockout-decorators)
• Optimizations for popular WC-libraries as long as it doesn't conflict with the generic/agnostic/unopinionated requirement
• Performance over ancient browser compatibility
• SSR ready? Google is betting heavy on this. The even deprioritized finishing the Material Design Components WCs in lieu of refactoring the existing ones to be SSR ready. (https://github.com/material-components/material-components-web-components/issues/1330#issuecomment-632386848)
• Electron (and similar frameworks) ready. CSP safe, etc.

Community goals

• >=IE8 compatibility?
• CLI to get started quickly, providing a quick access to templates with popular WC-libraries, but not forcing any of them on the user
• Nice looking website
• Great documentation
• Tutorials