Re: [w3c/browser-payment-api] Drop array support for supported methods? (#549)

I respectfully disagree on two counts. The first is perhaps a nit -- it is not nearly impossible to *deprecate* things, it just may be nearly impossible to actually remove them. Plenty of other Web technology has been deprecated or changed after being in the wild. Secondly, I don't think this particular stuff is so "in the wild" yet that it's an unstoppable force. I do understand the potential technical debt that arises when things are rushed out the door -- and many of us in the WG argued this point earlier on a number of issues.

That being said, I also don't think this particular naming issue matters that much either way. Hopefully the biggest take away is that if we feel the need to expose this stuff to the wild early, we should always prefer singular names for properties because it's more natural (IMO) to allow something to become plural (by means of an array) than to go in the other direction. This lesson has been learned in a number of other communities and we should follow suit.

-- 
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/browser-payment-api/issues/549#issuecomment-309290909