Kevin Gibbons

@zenparsing Sorry, didn't mean to lecture! I'm just trying to sketch out where our meta-level disagreement seems to be. (Object-level, I also disagree that whatever complexities there are in the...

@zenparsing I think a lot of this comes down to actual disagreements, not refusal to acknowledge points of view. I don't know how to resolve disagreements other than talking for...

> First, I want to be really clear about language: it is essential that we not use the term "private field" to talk about instance variables, because one of the...

> Isn't this solvable by exposing a new trap that will be called when a non-trappable operation is about to occur? Part of the design of the current proposal [is...

> Because the `WeakMap` model would throw an error, I think we've already made it detectable. The error would be thrown inside of the class, where it's in a position...

> JS programmers already know how to initialize instance state. They do it by performing assignments within the body of a constructor. I think that a huge fraction of people...

> In which standard edition of ECMAScript can you do that? Notice my careful phrasing of "people who would think of themselves as JS programmers".

@RyanCavanaugh, > evaluate the initialization expression once during class setup and copy that value to each instance [...] ~50% of devs will tell you this is the wrong behavior I...

> Instead, this proposal is an attempt to fight back against overall complexity. I definitely feel the complexity budget squeeze as the language continues growing. But... I guess I really...

@zenparsing, > but to the full set of class features that are either in some form of development or have been deferred to future proposals. That is a large list,...