Simplify our code base; can-observation reader has to know about every type, but with can-reflect, it shouldn’t
Higher-performing observables; can-compute is used everywhere, but we have some compute-like things that are faster, like can-observation; can-stache will use lighter-weight observables but the public API (computes) won’t change; can-define getters can also use can-observation instead of can-compute
Improve compatibility with other data types in an abstract way, e.g. streams can be observable in stache
Overview: self-closing can-import is static while using can-import with a separate closing tag is dynamic
Problems: it’s confusing to have different behavior based on whether an element is self-closing or not; also in the dynamic syntax, the component isn’t immediately available
Potential solutions: teach new syntax (hopefully keep backwards compatibility); maybe add late-binding for components