Re:Use cases for ES6 proxies
by tlrobinson on Wednesday July 20, 2016 @04:05AM
(#12127500)
People have been doing pseudo-classical inheritance in JavaScript since forever ago, but every framework had their own slightly different way of doing it. Might as well give them a "blessed" syntax to standardize on.
[ Parent
| on HN ]
Re:Use cases for ES6 proxies
by allendoerfer on Wednesday July 20, 2016 @04:46AM
(#12127636)
Why? If I am programming in Angular it does not matter what React is doing and whether they are using the blessed syntax or not.
I can't help but say it - but nobody programs in Angular or React, people program in JavaScript. When using a framework like Angular or React there are plenty of reasons to use ES6 classes, whether in the view code, or in more idiosyncratic app actors like utils or business logic ... the benefits of having a standardised syntax should be obvious. Likewise, many people contribute to these libraries and frameworks, again using a standard syntax for common patterns is obviously beneficial to my mind.
Re:Use cases for ES6 proxies
by allendoerfer on Wednesday July 20, 2016 @07:37AM
(#12128223)
I was just illustrating the fact that there are already communities with standards. It is fine for me that some use CoffeeScript or TypeScript. There are much smaller communities in other programming languages, which also work great, so I don't see a benefit in combining them. In the contrary I would say most of the time the bigger the community gets the lower the standard falls.