search

tc39 / proposal-class-fields

Orthogonally-informed combination of public and private fields proposals
https://arai-a.github.io/ecma262-compare/?pr=1668
1.72k stars 113 forks source link

Another community feedback #180

Closed hax closed 5 years ago

hax commented 5 years ago

I've given 3 hours speech about the class fields proposal yesterday (2018-12-09 16:00 ~ 19:00 Beijing time) in Hangzhou NodeParty.

The weather is not good (cold wave and snowy), but we still have about 100 attendees. We also have 1000+ online watchers (this is the peak value, not sure how many watch my speech).

In the end of talk, I did a poll on site. The options are

I don't have very accurate result, because it's a raising hand poll. Here is the rough result:

I will publish my slides this week and create a github repo for Chinese programmers further discussion.

hax commented 5 years ago

Another interesting onsite polls in the speech:

  1. [[Define]] VS [[Set]], < 10 chose [[Define]], > 30 chose [[Set]], most do not want to raise their hand anyway even I already ask them you have to make choice 😜
  2. [[Define]] VS [[Set]] Vs [[Define]] but change syntax (for example add keyword), some people originally choose [[Define]] or [[Set]] switch to [[Define]] but change syntax, but most people still refuse to raise hand
  3. [[Define]] VS [[Set]] VS [[Define]] but change syntax VS syntax sugar for getter/setter wrapper of private: [[Define]] < 5, [[Set]] < 10, [[Define]] change syntax < 10, most (not very accurate but at least 60%+) chose the last.
hax commented 5 years ago

Video (in Chinese, no English translation available)

https://www.youtube.com/watch?v=WDsEvlXE-BE

And it's incomplete , no first 15 mins, no last hour.

littledan commented 5 years ago

Thanks for this effort. I think it's always great to educate more people about language design and these sorts of tradeoffs, even if we disagree about the best way forward here. Let's follow up in https://github.com/littledan/js-outreach-groups/issues/6#issuecomment-448494578 for next steps for improving the relationship with the Chinese JavaScript community.