Re: Question of the Day: What about all this asynchrony?

On Wed, Nov 8, 2017 at 10:03 PM, Till Schneidereit wrote: > (Also FTR, I don't think the discussions you're starting here and > the way you're going about it and ignoring feedback people give > you is very productive, but that's all I'm going to say on the > matter.)

Re: Question of the Day: What about all this asynchrony?

On Wed, Nov 8, 2017 at 7:05 PM, kai zhu wrote: > > many of theses issues wouldn't exist if tc39 had responsibly > gatekeeped es6 with a more modest feature-set of languages-changes They did. You just disagree with the decisions that were taken, unlike the vast, overwhelming

Re: Question of the Day: What about all this asynchrony?

On Wed, Nov 8, 2017 at 7:05 PM, Michael Lewis wrote: > I don't want to break the rules and get removed from the list. But it > seems this list is powered by mozilla, and not "owned" by TC39 anyway. And > because there are no official topic rules, I think that discussing aspects

Re: Question of the Day: What about all this asynchrony?

Wow dude... Again, you're trying to pick a fight. I'm not "publicly shaming" anyone, that's ridiculous. All I have to say is, just watch. On Wed, Nov 8, 2017 at 1:22 PM, Jeremy Martin wrote: > I don't represent TC39, and I don't like adding so much noise to this > list,

Re: Question of the Day: What about all this asynchrony?

Thank you for this, Jeremy. -Terence On 11/8/2017 10:00 AM, Jeremy Martin wrote: Michael, You are not alone in your frustrations. Many of your points are valid, have been voiced before, and will no doubt be voiced again. No one on here is unsympathetic to this, and many members of TC39, as

Re: Question of the Day: What about all this asynchrony?

I don't represent TC39, and I don't like adding so much noise to this list, so this will be my last reply on the topic. There's nothing fundamentally wrong with what you want, but you're barking up the wrong tree to get it: > This (not concerning themselves with the end users experience) is a >

Re: Question of the Day: What about all this asynchrony?

Michael, >> >> >> Lambasting TC39 for not formalizing and centralizing these educational >> resources -- a task that exists far outside of their charter -- is not >> productive. > > > This (not concerning themselves with the end users experience) is a mistake > (an opinion). The JavaScript

Re: Question of the Day: What about all this asynchrony?

criticizing tc39 for the current problems in frontend-development is fair-game. many of theses issues wouldn't exist if tc39 had responsibly gatekeeped es6 with a more modest feature-set of languages-changes, instead of creating an entirely new language. On 11/9/17, Michael Lewis

Re: Question of the Day: What about all this asynchrony?

On Wed, Nov 8, 2017 at 10:00 AM, Jeremy Martin wrote: > Michael, > > You are not alone in your frustrations. Many of your points are valid, > have been voiced before, and will no doubt be voiced again. No one on here > is unsympathetic to this, and many members of TC39, as

Re: Web Docs

Interesting, thanks. I'll have to dig into it a bit more later. On Wed, Nov 8, 2017 at 9:56 AM, kai zhu wrote: > fyi, > mozilla recently created a webpage to publicize its position on open > Web and Web-related specifications submitted to standards bodies like > the IETF,

Re: Question of the Day: What about all this asynchrony?

Michael, You are not alone in your frustrations. Many of your points are valid, have been voiced before, and will no doubt be voiced again. No one on here is unsympathetic to this, and many members of TC39, as well as other community members, dedicate significant amounts of time, freely, to

Re: Web Docs

fyi, mozilla recently created a webpage to publicize its position on open Web and Web-related specifications submitted to standards bodies like the IETF, W3C, and Ecma TC39 @ https://mozilla.github.io/standards-positions/ the process to ask them for a position is to file a github issue @

Re: Question of the Day: What about all this asynchrony?

I did help you. I answered your question: I said async functions are preferable over all the other alternatives. And I said others can weigh in with their own perspective if they disagree. Of course TC39 justifies their decisions: but it's left up to us, as the developers, to find out what the

Re: Question of the Day: What about all this asynchrony?

I was hoping the last message was a one-off. As it now clearly isn't... Michael, along with all the other feedback you've received, please DO NOT swear on this list. This is a professional environment. It's entirely possible to express oneself clearly (and, er, concisely) without resorting to

Re: Question of the Day: What about all this asynchrony?

How difficult is it for a web developer to make a website? What if everyone in this mailing list shared their personal websites, and we ranked them? Not that mine is great, but at least I'm admitting that it's really fucking hard to make a simple website... I know a *lot *of web developers that

Re: Question of the Day: What about all this asynchrony?

So, the group that designs the language that the world uses for building web apps, cannot provide insight as to why they do what they do? Smells like bullshit. Maybe you can expand on that part further? Check this out. It seems the ECMA/TC39 group

Re: Question of the Day: What about all this asynchrony?

Hi Michael! TC39 is rightfully reluctant to offer usage advice. People should develop their best practices from experiences and the use cases they're involved in. For me, to answer your question, since I'm not a TC39 member, it's async functions all the way, and ditch observables, raw promises,

Re: Question of the Day: What about all this asynchrony?

Hi Felipe, I read and generally understand your points (while I don't fully understand all the new async syntax and best practices ). You agree that there's a lot to learn, but nobody