- From: Anne van Kesteren <annevk@annevk.nl>
- Date: Sat, 4 Oct 2014 08:28:00 +0200
- To: public-media-capture@w3.org
Can someone explain to me what the point of not deprecating a known-bad-thing is? Note that deprecating does not mean immediate removal. Just issueing warnings that it will be removed down the line and indicating what the replacement is. If you don't do that, I don't see why it's realistic to think you can deprecate it in two years time. The facts as I know them are: * The WebRTC API is prefixed in implementations * Promises are stable and shipping unprefixed (this was the holdout argument last year, if you remember) * It is hard to remove deployed features on the web That seems like a more than ideal position to move to promises when unprefixing happens. Perhaps supporting callbacks for a while to ease transition. Why is this not tenable? -- https://annevankesteren.nl/
Received on Saturday, 4 October 2014 06:28:27 UTC