> If you need to protect values in your class from malicious actors, you should use mechanisms that offer hard runtime privacy, such as closures, WeakMaps, or private fields.

I mean yeah, but doesn't that expose the public/protected/private propaganda as shallow? I know that there are other reasons to use public/private (like building a more parseable and granular #API), but the main thing there is still the subliminal desire to protect the precious secrets of the object. Which never happens with public/private, actually. We've been lied to. Like with many other things about #TypeScript.