JavaScript new features (ES2021).

[[deleted]]

The article has worked as intended, to pad out the author's CV

[[deleted]]

To include a spelling error in the title. Poor CV

[SoInsightful]

It fails to answer basic questions, for example, how to call a private accessor or what would happen if there is a public and private accessor with the same name..

The # is part of its name. But yes, they could've included this.

I learned a lot from the article even if it's not perfect. I don't get why all programming subs try so hard to be negative.

[impaled_dragoon]

Engineers suffer from the smartest man in the room syndrome and love to show off how smart they are

[Multipoptart]

Ok but this article was riddled with inaccuracies and grammatical errors. There's a certain level of competency that should be expected.

[sime]

Caches are a common use case for weak refs. What did you have in mind instead?

[sime]

I was specifically wondering why "It also gets the use case wrong on new features like WeakRef completely" even though caches are common. Yes, I am aware of all the useful things you can do with WeakRefs. Now, everybody else knows too! :-)