Re: [heycam/webidl] Differences between "normal" platform objects and "normal" JavaScript classes (#226)

> It would be really great if the standards venue didn't affect the shape of the resulting API.

Yes, it would, though we have a _huge_ legacy of it having done just that.  We had this exact conversation 4-5 years ago (not you and I, but various people involved in ES and web specs) and absolutely nothing changed as a result.  :(

> Would it be reasonable to start a policy of doing things in a more ES-type style

Why not in a more IDL-type style?  Honest question, not trolling.

> For enumerability on the JS side, there seems to be a strong feeling in TC39 that we couldn't add more enumerable methods to existing objects without breaking existing code.

Oh, on the DOM side we can't _remove_ enumerability from existing objects without breaking existing code.  Or more precisely, we know there are some we can't remove it from, but we don't know which things are in that bucket, necessarily.

This is all be a discussion about _new_ things that are added; for existing stuff we're stuck with what we have, I'm afraid.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/heycam/webidl/issues/226#issuecomment-258945843