kai zhu

operationally, how many of you would actually enjoy maintaining web-projects with polymorphic-classes with subclassed-properties having the same names as [unobservable] private-fields? this feels like a low-level hammer for low-level general-purpose...

@trotyl, the problem is deeper than that. i feel the whole class-based approach to solving async, UX-workflow problems commonly encountered in javascript is flawed. class-methods are ok for blocking-code design-patterns...

> but OTOH, exposing internal implementation details that some developers might not even realize they're exposing is arguably worse, so hard private is a better default from that perspective. how...

@ljharb nobody mixes crypto, credit-card, password, etc. with untrusted javascript code regardless if it's encapsulated or not. one does not see untrusted-code/ads running on merchant's payment webpage, and private-fields is...

- took a stab at this feature early on as maintainer, but felt too unfamiliar with codebase at time - open to external pull-requests - good starting-point in codebase would...