Re: styleguide sanity-check for tc39 language-proposals to address javascript-fatigue

2017-10-18 Thread Naveen Chawla
I disagree that the language contributors should be involved in best practice guidance. Patterns evolve over usage and experience with the constructs. I bet the implementors of `&&` and `||` didn't necessarily expect them to be used so effectively for non-boolean logic e.g. `car && car.drive()`

Re: styleguide sanity-check for tc39 language-proposals to address javascript-fatigue

2017-10-18 Thread Alexander Jones
The beauty of (coding) standards is that there are so many to choose from. :) IMO it’s a false dichotomy though. A respected and credible group of language contributors should pool some energy together and ratify some opinionated best practices, a la the C++ Core Guidelines and PEP-8. No, it’s

Re: styleguide sanity-check for tc39 language-proposals to address javascript-fatigue

2017-10-18 Thread T.J. Crowder
On Wed, Oct 18, 2017 at 8:18 AM, kai zhu wrote: > > its a legitimate agenda from someone who cares deeply about > javascript and believes es6 was a mistake and a step in the > wrong-direction for javascript and frontend-development. I won't get into an argument with you

Re: styleguide sanity-check for tc39 language-proposals to address javascript-fatigue

2017-10-18 Thread kai zhu
> Frankly, this just seems like you're trying once again to push your "JavaScript should have frozen in time as of ES3 or maybe ES5" agenda, which I don't think anyone else on this list shares. its a legitimate agenda from someone who cares deeply about javascript and believes es6 was a mistake

Re: styleguide sanity-check for tc39 language-proposals to address javascript-fatigue

2017-10-18 Thread T.J. Crowder
On Wed, Oct 18, 2017 at 6:44 AM, kai zhu wrote: > > there are several factors for the current javascript-fatigue. I don't believe any such thing exists. > es6/es7/es8 introduces hundreds of these kinds of questions > which distract us from actual coding and shipping

Re: styleguide sanity-check for tc39 language-proposals to address javascript-fatigue

2017-10-18 Thread Naveen Chawla
My opinions: For existing code, just transition when encountering code, for convenience (no need to transition everything in a go). For new code, always use await async where possible (very manageable vs callbacks) For new code, always use const (for references you don't expect to change) and

Re: styleguide sanity-check for tc39 language-proposals to address javascript-fatigue

2017-10-18 Thread Jordan Harband
These questions have consumed programmers in most languages since forever. It's not TC39's place to tell people how to write code - but there's plenty of style guides that have answers to these questions. On Tue, Oct 17, 2017 at 10:44 PM, kai zhu wrote: > there are several