I want to agree with po from an entirely different point of view--a non-programmer often trying to figure out how a particular program (in a language I don't know) works.
If I spot the "my" or "my-" prefix, I take it that the corresponding token (e.g. "mypref", "my-limit") is not a reserved term of the language, but one the programmer is defining or assigning. So the "my" prefix can be helpful (at least to some non-programmers) and I don't want it co-opted to become a reserved word.
Just for complete clairty, my-* does in fact indicate a token that the author/programmer is defining (a custom property), in the same way that data-* properties do in HTML, which is why my-* was used. But I understand that you dislike it and I can appreciate why. As I mentioned to Po, the draft is open on github, and you are free to make better suggestions here as well... I don't think anyone is particularly married to my- we do know that var- and data- have caused what we think was unnecessary confusion. Set- was proposed and denied. What are your thoughts - that's what this is all about. Let's not wind up with something that people find unintuitive if as a community we can make it better.
