What's with people liking custom elements? I feel the only argument going for them is: "it's globally scoped XML" - and not sure that's good
-
well, they feel native — you use <audio> and it creates an audio player, use <google-map> and it creates a map — all in HTML
not quite - first you need to define what <google-map> is using JS in the first place; I feel `GoogleMap()` is equally descriptive
-
-
but in theory browsers and screen readers could somehow know what <google-map> is, maybe with a manifest
-
that's quite speculative hey. Accessibility is possible now, as long as HTML is used, which like webcomponents, functions can do too
- 5 more replies
New conversation -
-
-
functions can just return data or do whatever, while elements hint that they will render UI of some sort
-
require('google-maps-component') seems pretty clear to me - there exists no cure for bad naming, except learning to name things well
End of conversation
New conversation -
-
-
and element mounting happens in HTML source, not in JS, which feels more intuitive, maybe just a habit “from the past”
-
I never have an "HTML" source - all glue happens in JS for me; trudging through forests of files or inline script tags seems horrid
End of conversation
New conversation -
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.