| > It's still pretty standard to compile es6 down to at least es2015 Yea, but that means if I want to use your library, I need a build chain. It used to be I could just do require("you") or <script src="you"> and be done with it. That's what we lost. Actually I need n buildchains, one for each npm module I use. And they better all be compatible and target at least one common runtime. And that better be a runtime I am comfortable deploying for my app. > I've also literally never met anyone who thinks that callback-structured code is "not a problem" Well here I am. Pleased to meet you. Might I also point you at: http://callbackhell.com There are many of us. I think what this really shows is how much professional ES6 programmers live in a filter bubble. This also explains why you think "just transpile" is a reasonable substitute for a simple, run-anywhere language. Professional ES6 programmers think everyone has 40 hours a week of paid time to spend maintaining a build chain. Javascript+Node used to be one of few languages that you could use without a build system. That's no longer the case. Maybe the loss was worth it to you. Fine. Makes sense. I wish more people would just acknowledge something has been lost, and that amateurs are struggling now at the expense of pros. |