cross-project-council VS proposal-class-fields

Since then, Node.js is being governed by the OpenJS Foundation. Now, the project is in good hands having people like James Snell from Snyk, Michael Dawson from Red Hat, and Matteo Collina formerly from NearForm in its Technical Steering Committee - tirelessly driving success, assessing latest developments in the field, and keeping the legend of Ryan alive!

It provided a structured environment for collaboration, partnership, and feature prioritization. In 2019 it merged with the JS Foundation to become the even more powerful OpenJS Foundation.

Node also has a foundation https://openjsf.org/ that could do similar governance and centralization. There is even a process to bring something like a framework of libraries https://openjsf.org/projects/ to the community.

This guy should approach the OpenJS Foundation [0] (previously it was the JQuery Foundation). It's sponsored by the big guys. There are a few more Open Source Foundation.

Could be that successfully funded OS projects are being maintained/leaded by charismatic guys? Those that can do marketing and get the project known and eventually get fundings. e.g.: tailwind, jquery, vue, sveltekit

0: https://openjsf.org

Bu vaqt mobaynida esa TC39 deb nomlangan JSni stardartlashtirish guruhi bir qancha OpenJS Foundation kabi ochiq jamiyatlar yordamida ECMAScript 2015 yoki ES6 versiyasini ishlab chiqishdi va 2015 yilga kelibgina taqdim etishdi. Bu JS tarixidagi shu paytgacha kirtilgan eng katta va muhim yangilanish edi.

This certification is offered by the OpenJS Foundation, a leading foundation that supports the growth and governance of many NodeJS open source projects such as Node.js, Electron, jQuery, and Webpack.

Code of Conduct

Private methods: Pretty simple to explain, private methods and fields straight up do not work with ES6 proxies, its a known issue https://github.com/tc39/proposal-class-fields/issues/106

The #x syntax is ugly and many people don't like it. But if you understand how JavaScript works, you'll see that private x is not possible. Some comments on the proposal suggested private #x and there were plenty of other suggestions as well, it may be interesting to read through those discussions.

> - # private... not sure why they didn't just use the "private" keyword, but I don't care. I almost always use TypeScript anyways

One of the reasons was to allow private and public fields of the same name, so that subclasses are free to add own public fields without accidentally discovering private fields. There were many more considerations that went into the design: https://github.com/tc39/proposal-class-fields/blob/main/PRIV....

There was a heated debate about this and the choice of the # sigil back in 2015 at the time private fields were being designed: https://github.com/tc39/proposal-private-fields/issues/14.

Private class fieldlari va nihoyat classlarda access modifierlarni (private,static) qo'llash imkonini beruvchi sintaksis.

class App extends React.Component { constructor(props) { super(props); this.state = { counter: 0 }; }} but due to Babel's class-field support, I don't use it anymore

I am using ReactJS with Babel and Webpack and using ES6 as well as the proposed class fields for arrow functions. I understand that arrow functions make things more efficient by not recreating the functions each render similar to how binding in the constructor works. However, I am not 100% sure if I am using them correctly. The following is a simplified section of my code in three different files.

Working with constructor and calling super() before we can set state. Although this has been solved with the introduction of class fields in JavaScript, Hooks still provide a simpler API