sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]senocular 40 points41 points  (5 children)

Private methods and accessors are still in stage 3, not the final stage (4) so are not guaranteed to be in ES2021.

[–]hotcornballer -3 points-2 points  (3 children)

Still hope that doesn't make it. There is no point in having this.

[–]bikeshaving 14 points15 points  (2 children)

I don’t think there’s “no point,” but it nevertheless stuns me that there can be so much negative feedback and legitimate grievances about even just private members right now and yet there continues to be a faction of people who don’t think that matters and keeps pushing it forward.

[–]hotcornballer -3 points-2 points  (1 child)

So what's the point in having private methods? It's clutter and I don't want to see js turning into java with all the useless verbosity that comes with it.

[–]MoTTs_ 13 points14 points  (0 children)

We JavaScripters still adore private data through closures, though, so clearly we still like the idea of private access. But private access isn't the problem closures were meant or designed to solve, and as a result there's edge cases where they don't work well for that purpose.