On Tuesday, February 18, 2014 4:59:51 PM UTC-4, John Messerly wrote: > > yeah, I guess to me, those reasons aren't worth the mental overhead for > having two ways of doing the same thing. Since people can choose "publish", > humans and tools can't really rely on "attributes" telling the full story, > so it kind of undermines the declarative value of "attributes". Honestly I > would be fine with either "attributes" or "publish" if it was the only way. > Anyway, just my opinion FWIW :) > > I'm in the same boat. If either was the 'one way' then I'd be fine with it, but at the moment, I virtually always use @published annotation. Some cases just because if I want to change an @observable to an attribute it's much easier to just change the annotation. And the other is because I find it much easier to work with just one file after I get the base HTML stuff written, and worry about only the code as I refactor etc.
Just my $0.02CDN =) Matt Follow Polymer on Google+: plus.google.com/107187849809354688692 --- You received this message because you are subscribed to the Google Groups "Polymer" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/3d9b180d-cd30-47f1-a23a-42c84557ea00%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
