Make the world a better place? Remove some JavaScript from it

When it's framed as "Remove JS from the world to make it better", that invites a lot of drama.

When I was learning JS (coming from Python) I hated async programming, but it was mainly due to the syntax of callback hell. I couldn't tell what would run after what because it was no longer in order in my source code.

As other have noted async/await syntax fixes that problem. Since 3.5 that's available in standard Python (and the concepts have been in use in packages like Tornado for ages).

So ultimately I think we will see an explosion of languages that run in browsers, I don't think hiding core concepts is helpful to that endeavor.

I loved the example off "amount off code needed in js...".

These statements make me laugh by default. Amount off code needed in these contexts is so relative.

U can write 3 functions, chain them as promise/callbacks, then make it an exportable module, and it becomes:

"var x = require('x');"

Wow 1 line off code, to reference all that code off the functions, and 1 or 2 more for the options/arguments.

There's an inherit complexity and amount of code needed due to the nature off "variation" and odd cases. Creating an app that does a 100 different things will likely need more code than when it does one thing.

That said, nothing stops you from decoupling it, and create a higher leveled file to create a virtual "hub", where u do nothing more than chain the modules and give args. Basically like Node.

I can only imagine the pain of using Skulpt (JS interop + Debugging). I might be wrong in my assumptions, any feedback from Skulp devs here?

> And here’s how you’d do it in Javascript. I count three separate callbacks here. I’m not exaggerating - this is an example straight from the documentation of the postgres library!

Yet this JS code is done on a mediocre way (for today, 2017). This code would be far shorter and easier if done in JS using async/await, which is what everybody should be using now.

So, besides that, there is the premise that using the same language in the browser AND in the server is a good thing; but how true is tat premise when the "alternate" language is pretty much similar in features? I mean, there's not such a huge benefit of going from JS to Python; perhaps i can concede that Python is mostly strongly typed (a good thing), but it's not like there were huge advantages.

And then, how hard is to go from Python to JS to C# to Java when these four languages are very similar in syntax, as well? Hard stuff, for a programmer, would be to jump from JS to Forth or to Prolog; radically different languages.

Yes there are type annotations, but they are just that at the moment, annotations. There isn't, as far as I know, a good type checker, or IDE that makes good use of them.

Ironically, an extended version of this transpiler could potentially be used to convert annotated python to Typescript. And poof! Proper type-checking in Python.