Re: [w3c/webcomponents] Why do we really need hyphens? (#658)

We already have a unifying module that does all that. it is called HTML.
Hence the still mostly unresolved (at least for my problem space)
discussions about HTML imports and modules and so on. I'm afraid i don't
have solutions though -- we work around this using thing like Vue and our
own internally developed workflows and libraries. There are several
staunchly entrenched combatants in these discussions unfortunately. We are
working around them until they reach consensus.

I hope folk go easy with the "everybody" part though. :) I personally don't
HATE the hyphens but this is really a namespace issue at the core. We came
out of the gate with this having to make a list of exceptions to the
allowed names. What we really need (and others smarter/deeper in
implementation of the spec than me) are ways to name things locally in any
way we chose.


On Fri, Aug 25, 2017 at 13:10 Joseph Orbegoso Pea <notifications@github.com>
wrote:

> I know this has already been discussed.
>
> But I think the web moves too slow for this to really be a problem.
>
> Many frameworks already allow this.
>
> For example, the new and highly popular Vue <http://vuejs.org> allows
> names without hyphens.
>
> Everyone LOVES it.
> ------------------------------
>
> What the web needs is perhaps to stop, and think about these new component
> models in a different way. For example, here's a proposal: the Unity
> Component Spec
> <https://github.com/TheLarkInn/unity-component-specification>.
>
> We simply just need a way to write components in a way where we can easily
> associate behaviors with any tag name. For example, if we want to define
> what <foo> means inside our component, let's be able to do that.
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/w3c/webcomponents/issues/658>, or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AGYGJxsKnJkbFdocwWzEvLYoV76OKk-eks5sbwAFgaJpZM4PC7rw>
> .
>


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/658#issuecomment-325009011