The real distinction lurking beneath the surface of this thread is not
between XML and HTML (though I agree that self-closing elements would be
nice and namespaces or at least aliasing will definitely be required) but
rather between the web as URL+API vs the web as URL+Markup. If markup
doesn't matter, then asm.js, DIV soup, famo.us and to some extent React may
well represent the future of web development -- and as was mentioned
before, we simply need to get over the warm and fuzzy feeling of being able
to "View Source" (which is effectively compiled). But if markup _does_
matter (for apps as well as docs), then surely making it extensible is a
winning move (i.e. open-ended vocabularies should be considered a blessing
not a curse).
I have a gut feeling that markup matters, even for apps (I enjoyed Adobe
Flex and OpenLaszlo was fun as well), but where are such projects now
(XUL?), and why is it so difficult to pinpoint the benefit of markup over
"js-compiled" solutions?
Manor.
On Sunday, October 20, 2013 11:57:41 AM UTC-4, Rob Dodson wrote:
>
> I think the most frequent gripe I hear about Web Components is that they
> look like XML and that totally freaks people out. I can definitely imagine
> my own horror if I were to open up a client project and top to bottom was
> all custom elements that I knew nothing about.
>
> My own opinion is that they're almost like jQuery plugins. I don't see
> much difference in:
>
> <div class="fancy-dropdown"></div>
> $('.fancy-dropdown').dropdown();
>
> and
>
> <fancy-dropdown></fancy-dropdown>
>
> and just like jQuery plugins, they're great if used in moderation but
> *horrible* if they constitute the bulk of your site. I realize that's not
> a very accurate analogy but I think it gets at my main point which is "If
> it does something mysterious then don't overuse it."
>
> I figure in time some custom elements might become so commonplace that
> they achieve the same level of mindshare as seeing $ or .btn does today.
> Bootstrap is a good example. If I opened a document and saw <twbs-btn> then
> I could say "Oh! I know how Bootstrap buttons work. OK, moving on...". So
> my hope is that the good stuff will rise to the top and the best practice
> will be "liberally use the good stuff, but go easy on the esoteric or
> lesser known elements."
>
> Does that make sense? What do you guys think?
>
>
>
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/57f37a96-70ed-4320-8f56-4e8b669ef7c7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
