@Raynos: it's important to acknowledge that there are many classes of app that don't need client models/compilers. /cc @jlongster
-
-
Replying to @slightlylate
@slightlylate@jlongster this is true, however web components are good for a subset of things (websites + prototypes). not ALL web apps.1 reply 0 retweets 0 likes -
Replying to @Raynos
@Raynos@slightlylate@jlongster This is what I mean by not knowing what the points are. That's a strong assertion, what's the reasoning?1 reply 0 retweets 0 likes -
Replying to @justinfagnani
@justinfagnani WC may be useful for web apps. However they are a choice compared to other frameworks.@slightlylate@jlongster1 reply 0 retweets 0 likes -
Replying to @Raynos
@Raynos@slightlylate@jlongster I still don't understand where the critique is in that statement. WCs aren't an either/or with frameworks3 replies 0 retweets 0 likes -
Replying to @justinfagnani
@justinfagnani@Raynos@slightlylate Critique is that there are few to no examples of shared low-level components. Only a framework.1 reply 0 retweets 0 likes -
Replying to @jlongster
@jlongster@Raynos@slightlylate Still confused. The Polymer project's core-* elements, and Mozilla's Brick elements are great examples.2 replies 0 retweets 0 likes -
Replying to @justinfagnani
@justinfagnani@Raynos@slightlylate And yet, basic questions are still unanswered about using them in something like Ember.1 reply 0 retweets 0 likes -
Replying to @jlongster
@jlongster@Raynos@slightlylate <core-button>. Done. Ember can handle elements, right?@wycats ?2 replies 0 retweets 0 likes -
Replying to @justinfagnani
@justinfagnani@Raynos@slightlylate@wycats no way to bind on-* events to ember's controllers, as far I know2 replies 0 retweets 0 likes
@jlongster @justinfagnani @Raynos @slightlylate it's all in the details. I'd like to see it work; nervous about "just an element" attitude
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.