JavaScript TC39 implementing hashmark private class fields

Re:JavaScript TC39 implementing hashmark private class fields by just_astounded on Thursday August 03, 2017 @02:46PM (#14922481)

I think the concern is that if you look here: https://github.com/tc39/proposal-private-fields/issues/14 and other places, you'll see this massive push back from the community, yet the proposal is moving forward regardless.

[ Parent | on HN ]

Re:JavaScript TC39 implementing hashmark private class fields by dmitriid on Thursday August 03, 2017 @03:48PM (#14923118)

Pushback from the community means nothing to TC39. Zilch. Zero. Nada.

The only instance of something dropped was cancelable observables. AFAIR it was only because some other group at Google opposed it.

Everything else is carried full steam ahead. Enjoy your import() instead of the vastly superior System.loader. Enjoy your hashes as member access specifiers. Dumpster fire. Template literals. BigInts. `new.target`. Dumpster fire. `import.meta`. Dumpster fire

[ Parent | on HN ]

Re:JavaScript TC39 implementing hashmark private class fields by just_astounded on Thursday August 03, 2017 @11:43PM (#14926168)

While it hasn't changed their minds, I do see the authors of the proposal actively discussing and engaging with the community. That's better than nothing, I suppose.

[ Parent | on HN ]

Re:JavaScript TC39 implementing hashmark private class fields by model_m_warrior on Thursday August 03, 2017 @02:51PM (#14922547)

Gotta get into the enterprise somehow. Even if that means bloating the language so its easier for the career desk jockeys to use (ie: dont ask them to learn something new).

[ Parent | on HN ]